manifest

/manifest — Full Autonomous SDLC

The complete end-to-end development flow. Four human gates. Everything else runs autonomously.

Gates (Human Approval Required)

GATE 1: Scope approval
GATE 2: Spec approval (after /conjure)
GATE 3: Plan approval (after /blueprint)
GATE 4: PR title and final go-ahead (before /seal)

Process

Phase 0: Scope Triage [GATE 1]

1. Ask: "What do you want to build?" (one sentence description). End your turn. Wait for their answer before assessing anything.
2. Assess scope — is this one coherent feature or multiple independent subsystems?
3. If too large: help decompose into sub-features, each with its own /manifest cycle
4. Present scope to user. End your turn. Wait for explicit approval before proceeding to Phase 1.

Phase 1: Design [GATE 2]

5. Run /conjure — full design dialogue
6. Write spec to .workspace/shared/specs/
7. Wait for spec approval.

Phase 2: Planning [GATE 3]

8. Run /blueprint — create task plan with parallelism map
9. Write plan to .workspace/shared/plans/
10. Wait for plan approval. Do NOT proceed to Phase 3 until explicit approval arrives.

Phase 3: Isolation [GATE 3.5]

11. Propose a branch name derived from the feature (e.g. feature/<kebab-case-name>). Ask:

    "Ready to create a worktree for isolation. I'll use branch feature/<name>. Create it now, or work directly on the current branch?" End your turn. Wait for their reply.

    • If they confirm: run /portal <name> — passes the name directly, no re-prompting
    • If they decline: note "working in current branch" and continue

Phase 4: Implementation

12. Proceed immediately after Phase 3 without waiting. Run /orchestrate — execute all tasks using parallel agents where safe, sequential where required
13. /ward discipline enforced throughout (TDD)

Phase 5: Verification

14. Run /certify — tests, types, lint, build, evidence collected

Phase 6: Review

15. Run /scrutinize — 3 specialist reviewers in parallel
16. Run /absorb — fix critical and high findings

Phase 7: Ship [GATE 4]

17. Run /certify again — clean state after review fixes
18. Ask user for PR title. Wait for approval.
19. Run /seal — simplify, commit, PR, monitor CI, merge

Autonomous Continuation

After each sub-skill completes and prints its completion signal, immediately proceed to the next phase. Do not stop and ask "should I continue?" unless the phase is a defined GATE. Blueprint ending with "Run /orchestrate…" is a signal it is done — manifest continues autonomously from there.

Reporting

After each phase, brief status: "Phase N complete: . Starting Phase N+1."

Completion Signal

"Manifest complete. Feature shipped. Chronicle will record this session at stop."