knowledge-mcp: Skill for Claude Code

Prefill: $ARGUMENTS

For pipeline discipline (background spawns, one writer per artifact, verdict routing) reference /orchestrate. This skill is prefill-specific.

Step 0: Gate on the ticket

Fetch the ticket by id with metadata. metadata.validated must be present and name a research node; without it, stop and route to /research. Read the ticket's open items: an undecided design the user owns is settled with the user before a planner spawns, never left for the planner.

manage({"operation":"status"}); collect if the index is behind the tree the ticket lands on.

Step 1: Spawn the planner (background)

One planner, one prefill. The brief carries the ticket id, the tree and branch to resolve at, sibling work in flight on the same branch with its touched files, the user's load-bearing rules verbatim, and the reads to stamp. It names no design and no mechanism.

Agent(subagent_type: "planner",
      prompt: "Produce the prefill for ticket <id> at <tree> on <branch>, per the prefill rulebook: no steps, every line resolved by tool with its command, the what-to-test list covering every numbered requirement, the harnesses that reach each seam. Siblings in flight: <list or none>. Deliver the report to main.",
      description: "Prefill: <ticket>",
      run_in_background: true)

Step 1a: Settle open items before anything freezes

When the planner's report carries open items, settle every one the ticket, the user's rules or memory already answers, and route the rest to the user, before resolving citations. Each settlement goes back to the planner that raised it, idle with its context intact, to incorporate into the prefill. The prefill is not frozen for review until that planner has read the settlement back into the node. At reviewer spawn the ticket's updated_at is older than the prefill's, or the prefill goes back to the planner first. A ticket amendment after that point reopens the prefill, never the audit.