documentlisted

# Document Command Creates minimal, proportional documentation. Match doc weight to change weight. One agent does the steps in order. ## Usage ``` /sf:document [SPECIFICATION_AND_IMPLEMENTATION_PATHS] ``` ## Context Read `.sf/implementation-summary.md` if it exists. ## Input Resolution 1. If `$ARGUMENTS` is non-empty: use it as the artifact and implementation paths 2. Else if `.sf/spec.md` and `.sf/implementation-summary.md` exist: use them 3. Else: ask the user where the artifacts are. Wait for the answer. ## Execution Write each file in turn. All paths are under `$SF_DIR/research/`. 1. `artifacts-summary.md` — the requirements and outcomes in the artifacts. Read only what exists. 2. `implementation-summary.md` — the real code structure: the main files, the changed interfaces. 3. `docs-inventory.md` — every existing doc as `filepath | primary topic`, from the headings only. **Gate 1 — Post-Analysis:** run `scripts/doc-gates.sh analysis`, in this skill directory. **If doc-gates.sh fails (non-zero exit), halt immediately — do not write the documents.** 4. `technical-docs.md` — what a developer needs to use or extend the change. Skip any section that does not apply. 5. `user-docs.md` — only what the user must do differently. Skip it if the change is invisible. An empty file is a valid result. It means the change does not need that document. **Gate 2 — Post-Generation:** run `scripts/doc-gates.sh generation`. **If doc-gates.sh fails (non-zero exit), halt immediat