Agent skill
10-01-open-questions-system
Track and resolve open questions in Obsidian comments using emoji markers and block IDs.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/10-01-open-questions-system
SKILL.md
10.01 Open Questions System
Track open questions in Obsidian comments using a consistent format so questions can be searched, referenced, and resolved in context.
- Reply in-line until the conversation is resolved.
- Multi-line is allowed if it improves readability.
- The same system applies to code — syntax varies by language (e.g.,
// 🙋♂️).
One-Shot Usage (LLM)
- Use the comment format below.
- Add a block ID to every question.
- Last emoji decides whose turn it is.
- Mark resolved with
✅in place.
Comment Format
%% 🙋♂️ Human question/task %% ^q-scope-topic
%% 🤖 Agent question waiting on human %% ^q-scope-topic
%% 🤖 Agent question waiting on human 🙋♂️ human answers %% ^q-scope-topic
%% 🤖 Agent question waiting on human 🙋♂️ human answers 🤖 asks more 🙋♂️ sure why not %% ^q-scope-topic
Completed → mark as done in-place (and optionally copy to [[playbook/10-docs/10-02-question-archive/SKILL]]):
%% ✅ Question here → Answer here %% ^q-scope-topic
Markers
| Marker | Meaning | Who acts next |
|---|---|---|
| 🙋♂️ | Human wrote this | Agent acts |
| 🤖 | Agent wrote this | Human responds |
| ✅ | Done | - |
Rules
- Blank line between questions. (Obsidian merges adjacent comments.)
- Every question needs a block id. Use
^q-{scope}-{descriptor}. - Last emoji decides whose turn it is.
✅means done.
Finding Questions
Terminal search:
rg "🙋♂️" docs/
rg "🤖" docs/
rg "✅" docs/
rg "%% .*%%$" docs/ # missing block IDs (lines ending with %%)
rg "🙋♂️" src/
Obsidian search:
🙋♂️for human tasks🤖for agent questions
Linking to a Question
[[features/10-core/10-01-spec#^q-prediction-fixed-tick|Prediction tick question]]
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?