10 03 Obsidian Flow
Productivity10-03-obsidian-flow10 03 Obsidian Flow is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
How documentation stays aligned with code using AGENTS.md, open questions, tk tickets, and Johnny Decimal structure.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/documents/10-03-obsidian-flow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/10-03-obsidian-flow, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
10.03 Obsidian Documentation Flow
How documentation stays aligned with code.
AGENTS.mdin code/source folders for folder-level rulesdocs/playbook/for process/toolingdocs/reference/for architecture and researchdocs/features/for documenting work/spec
Core Rules
- AGENTS in code folders. Every top-level code/source folder needs an
AGENTS.mddescribing purpose, boundaries, entry points, and tests. - Open questions live in docs. Use
🙋♂️/🤖/✅comments with block IDs. See [[playbook/10-docs/10-01-open-questions-system/SKILL]]. - Use
tk+tinychange. Create atkticket for non-trivial work and update the changelog viatinychange. Use the standard ticket template. Don't manually update the changelog. - Johnny Decimal (two-digit). Use
NN.NNfor playbook/reference IDs.
One-Shot Usage (LLM)
- Read
docs/AGENTS.mdand the closest folderAGENTS.md. - Update playbook/reference docs, not sidecars.
- Use open-questions format with block IDs.
- Record a
tkticket for non-trivial work. - Log changes:
tinychange -I new -k <fix|test|chore|security|feat|docs|refactor|perf> -m "message" -a AUTHOR
When Updating Code
- Read the nearest
AGENTS.mdin the code folder. - Update or add
AGENTS.mdif the folder's purpose/boundaries changed. (ONLY ALLOWED AFTER[OK]from the Hooman.) - If behavior changes, update the relevant docs in
docs/reference/. - Log the change via
tinychange.
Where to Document
- Process/tooling →
docs/playbook/ - Research →
docs/reference/ - Feature specs/plans →
docs/features/ - Architecture →
**/AGENTS.md