Doc Add

Creating a document. Every type follows the same four beats — scaffold, fill, wire, commit — so this is one skill and a table, and the table says what differs per type.

This verb creates the artefact and nothing else. Picking up a unit of work is compass-agile-start-task: that one branches, stamps the journal, and moves state.

1. Pick the type. Unsure which document a thing is? Take the first match in the placement procedure in Skill naming conventions. Then find its row in the table below.

2. Scaffold it with the row's command. Compass fills the frontmatter and generates the :ID:, so never hand-write either.

   ./projects/ores.compass/compass.sh add knowledge --slug my_topic --title "My topic"
   

   The row's Lands in column says where it goes. Where that column names a default, compass derives the parent from where you are, and --parent-dir overrides it.

3. Fill every section the row names. A scaffold left with its placeholder prose is worse than no document: it reads as content and says nothing. Use the real generated :ID: values in any links you add.
4. Wire the parent index. A document nothing links to is invisible to search and to the graph, whatever its content. A story wires into the sprint's * Stories table, a task into its story's * Tasks table, knowledge into its topic index, a recipe into its topic page.
5. Commit per commit conventions, with the component bracket the type calls for: [agile] for a story or task, the bucket name for a capture, [doc] for the rest.

• How do I create a new doc?
• How do I add a doc with compass?

• Document types — the contract each type in the table above must meet.
• Skill architecture — why a uniform verb is one skill plus a type table.