Setup

Register the workflow's output locations in the project's memory file. This is the only skill that ever writes to the memory file, and the only thing it writes there is one marker-wrapped index block — pointers, never content.

Rules

• Write one thing only: the <!-- setup:index --> block. Touch nothing else in the memory file — not even to fix typos.
• The index holds addresses, not content. Point at the canonical paths even when the files do not exist yet — their skills create them lazily.
• Ask in plain text, one line answerable. No checkbox tools.
• First write requires the user's explicit confirmation. If declined, do not write and do not re-ask within this run.

Steps

1. Find the memory file

• CLAUDE.md exists → that is the memory file.
• Else AGENTS.md exists → that is the memory file.
• Neither exists → the project has no injection channel. Ask: "No memory file found — create one so agent sessions start oriented? CLAUDE.md (Claude Code) or AGENTS.md (Codex and others), or skip." If skipped, stop and report.

2. Present the draft

The block is fixed — five entries, one line each:

<!-- setup:index -->
## Workflow Outputs

- Runtime configuration (verified by /setup-runtime): docs/agents/runtime.md
- House style (recorded by /setup-style): docs/house-style.md
- Domain glossary: CONTEXT.md
- Architecture decisions: docs/adr/
- Implementation blueprints: docs/plans/
<!-- /setup:index -->

In a multi-context repo, point the glossary entry at CONTEXT-MAP.md instead.

Ask: "Add this index block to {memory file}? It gives every agent session a map of the workflow's outputs."

3. Write

• Markers already present → replace the block between them (keep the markers). If the content is already identical, report "index up to date" and write nothing.
• No markers → on confirmation, append the block at the end of the file.
• If the user has hand-written pointers to the same paths elsewhere in the file, point them out and let the user remove the duplicates — do not edit those lines.

4. Handoff

Report what was written, then:

"Onboarding has two more steps: /setup-runtime verifies the dev loop and records the runtime configuration; /setup-style captures the team's coding conventions. Their outputs will already be indexed — run them when ready."