st-close

Files (1)

• SKILL.md

SKILL.md (first lines)

# /stratum:st-close

You are the orchestrator. You route and verify.
Plugin root (`<plugin root>`) is two levels up from this skill's base directory.

## 0. Start

1. Read `<project>/.stratum/state.json`. If there is no `feature_directory`, stop and tell the
   user to run `/stratum:st-define`.

## Steps

1. **Gap report or not.** If tasks.md has unticked tasks, make a gap report; otherwise skip
   it. Say which in one line; the user can override.
2. Start the `st-close` subagent (`stratum:st-close`) with absolute paths: plugin root, project
   root, feature dir, whether to make the gap report, and the base for the shortcut list. On a
   branch, the base is `main`. On `main`, the base is
   `git rev-parse "$(git log --diff-filter=A --format=%H -- <feature dir>/spec.md | tail -1)^"`.
   Tell it: the gap report follows `<plugin root>/procedures/converge.md` (`<PLUGIN_ROOT>` is the
   plugin root), steps 1 to 6 only.
3. **Verify.** Check each drift change against the code it names.
4. **Gaps.** For each gap, the user picks: send back, defer, or drop.
   - Send back is allowed once per feature. If tasks.md already has a `Convergence` phase, offer
     only defer or drop.
   - On send back: resume the same `st-close` with `SendMessage` to append the tasks (converge
     step 7), run `/stratum:st-build`, then run step 2 again without a gap report.
   - Defer and drop: `st-close` records them in spec.md.
5. **Lessons.** Make sure `<project>/.gitignore` has `.stratum/lessons.md`. Read the lessons from
   `<project>/.stratum/lessons.md`. `st-close` writes each there with its target file and the
   reason. For each, the user picks keep, another target, or drop. On keep,
   write the rule to the target file yourself.
   For a constitution target, bump its `**Version**` (MINOR for a new rule, per
   `<plugin root>/procedures/constitution.md` step 2) and set `**Last Amended**` to today. If the
   app constitution is missing, create it with that one rule, `**Version**` 1.0.0 and today's
   `**Last Amended**`. Then show the user the line `@.stratum/<app>-constitution.md` for the
   CLAUDE.md that loads in that app's worktrees. If `.stratum/constitution.md` is the target and
   is missing, tell the user and do not write the rule. For an ordinance target, create
   `apps/<app>/ORDINANCE.md` if it is missing, and make sure `apps/<app>/CLAUDE.md` has the line
   `@ORDINANCE.md` (create the file with that one line if it is missing). Show the user any other
   proposed constitution or harness change. Never apply one without their OK.
   Remove a dropped lesson from `.stratum/lessons.md` at once, and
   a kept lesson once its rule is in the target file. Every other lesson stays in it.
6. **Shortcuts.** `st-close` reports the rows from `scripts/st-shortcuts.sh`. Show each row.
   For each, the user picks fix now or keep.
   - Fix now: the `st-build` agent (`stratum:st-build`) fixes it, then verify with
     `bash <plugin root>/scripts/st-verify.sh '<test command>' <files touched>`. Then the `st-git`
     agent (`stratum:st-git`) commits the files the fix touched, with exact paths.
   - Keep: no record. The marker stays in the code, and `st-ponytail-debt` finds kept markers
     across the whole repo.
7. **Docs graph.** Run the `st-graphify` skill once to update the docs graph.
8. `st-git` commits the changed docs with exact paths, and the files step 5 wrote (never
   `.stratum/lessons.md`).
   After the commit lands, set `phase` to `done` in `<project>/.stratum/state.json` with `bash <plugin root>/scripts/st-state.sh <project>/.stratum/state.json phase done`.

## Gate

Report in short form: drift fixes, gaps and their fate, lessons, shortcuts and their fate. Then
say: "Say push to push." Push only on the user's "push".

## Always

- Never skip the commit guard. If a commit is blocked, tell the user; do not work around it.
- Push only when the user says "push".

From HyuseCS/stratum, MIT.

More from HyuseCS/stratum