st-plan

Files (1)

• SKILL.md

SKILL.md (first lines)

# /stratum:st-plan

You are the orchestrator. You route and verify; you do not write the plan yourself.
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. Start the `st-plan` subagent (`stratum:st-plan`). Pass absolute paths: plugin root, project
   root, feature dir. Tell it: follow `<plugin root>/procedures/plan.md`, then
   `<plugin root>/procedures/tasks.md`; `<PLUGIN_ROOT>` in those files is the plugin root; return
   open decisions as a list instead of guessing.
2. **Open decisions.** If it returns any, grill the user one decision at a time, each with the
   options and your recommendation. When all are answered, resume the **same** subagent with
   `SendMessage` (its agent ID) and the answers. Repeat until it reports no open decisions.
   A `[screen]` task's Design lane mode is an open decision like the others: the user picks autonomous or new look, and custom design only when `skills/st-design/SKILL.md` names a custom mode.
3. **Verify.** Check that `plan.md`, `research.md`, `quickstart.md` and `tasks.md` exist in the
   feature dir, that every FR has a test task before its build task, that every task names exact file paths,
   that every task names its exact test command (`Test:`), that every `[P]` task names the files it owns (`Owns:`) and no two `[P]` tasks in one phase own the same file, and that every `[screen]` task has its mode.
   Send gaps back to the same subagent.
4. **Advisor.** Run `bash <plugin root>/scripts/st-advisor.sh plan <feature dir>` from the project root in the foreground, with a Bash timeout of 600000 ms, and wait for it.
   Codex reads spec, plan and tasks in the read-only sandbox and only advises: a simpler or better approach, tasks to cut or merge. It does not validate; st-inspect does.
   Handle its answer as in "Advisor" in `<plugin root>/skills/st-build/SKILL.md`; big ones go to the user before the gate.
   Fixes go to the same `st-plan` subagent and cost a round.
5. Have `st-git` commit the plan files with exact paths, and `<feature dir>/advisor.md` if it changed.

## Gate

Next phase: `/stratum:st-inspect`.

## 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