feat(workflow) Spec status, plan deviations, lettered options, draft PRs per repo #34

Merged
araemer merged 5 commits from plan-feature-branches into main 2026-10-03 11:49:58 +00:00
Owner

Summary

  • Spec status (#26): every spec carries a status that follows the gates: Spec, Phase A: Contract, Phase B: Repo architecture, Phase C: Planning, Implementation, Review, Done. One status until GATE A, then one line per affected repo. Changes after GATE A go through a status PR that the user merges. The new shared skill recipe-workflow:spec-status owns that procedure and asks when an earlier status PR is still open. The po agent, plan-feature, implement-plan, implement-feature and review-feature set the status at their steps. Epics get a coarse Status column; E01 has it filled for specs A to F.
  • Plan deviations (#33): every plan ends with an append-only ## Deviations section. implement-plan appends an entry per deviation, and review-implementation treats listed deviations as agreed while checking them against the code.
  • Onboarding (#30): the workflow summary in ONBOARDING.md names the architect step and the gates.
  • Lettered options: the po and architect agents label the options of every question with letters, restarting at A per question.
  • Push every commit, one draft PR per repo: commit 066a445, pushed to this branch after #24 was merged.

Cross-cutting ADRs: docs/adr/2026-10-03-spec-status.md, docs/adr/2026-10-03-plan-deviations.md. Each changed skill and agent has its own ADR next to it.

Not in this PR

  • The status line of spec 002, which is on its own branch (#35). Spec 001 is set to Done for both repos here.
  • recipe-workflow:pr-feedback does not write deviation entries yet.
  • The Deviations section already in recipe-app/docs/plans/001-shopping-lists.md is not reformatted.

🤖 Generated with Claude Code

## Summary - **Spec status (#26):** every spec carries a status that follows the gates: Spec, Phase A: Contract, Phase B: Repo architecture, Phase C: Planning, Implementation, Review, Done. One status until GATE A, then one line per affected repo. Changes after GATE A go through a status PR that the user merges. The new shared skill `recipe-workflow:spec-status` owns that procedure and asks when an earlier status PR is still open. The `po` agent, `plan-feature`, `implement-plan`, `implement-feature` and `review-feature` set the status at their steps. Epics get a coarse Status column; E01 has it filled for specs A to F. - **Plan deviations (#33):** every plan ends with an append-only `## Deviations` section. `implement-plan` appends an entry per deviation, and `review-implementation` treats listed deviations as agreed while checking them against the code. - **Onboarding (#30):** the workflow summary in `ONBOARDING.md` names the architect step and the gates. - **Lettered options:** the `po` and `architect` agents label the options of every question with letters, restarting at A per question. - **Push every commit, one draft PR per repo:** commit 066a445, pushed to this branch after #24 was merged. Cross-cutting ADRs: `docs/adr/2026-10-03-spec-status.md`, `docs/adr/2026-10-03-plan-deviations.md`. Each changed skill and agent has its own ADR next to it. ## Not in this PR - The status line of spec 002, which is on its own branch (#35). Spec 001 is set to Done for both repos here. - `recipe-workflow:pr-feedback` does not write deviation entries yet. - The Deviations section already in `recipe-app/docs/plans/001-shopping-lists.md` is not reformatted. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Gate commits in plan-feature are pushed right away and open a draft PR
(WIP: prefix) in each affected sibling. implement-plan pushes every commit
and marks that draft ready instead of opening a second PR. CLAUDE.md gains
the "never commit without pushing" rule and the gate standing permission.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feat(workflow) Label the options of PO and architect questions with letters
All checks were successful
/ typecheck-contract (pull_request) Successful in 25s
e644491c22
The po and architect agents label the options of every question with
letters (A, B, C), restarting at A per question, and name the recommended
option by its letter, so the user can answer with a single letter. Each
agent gets an ADR for the change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The short workflow in ONBOARDING.md named /plan-feature without saying
that it starts with the architect agent and GATE A, followed by the repo
architects (GATE B) and the planners (GATE C). It also gains the PR
feedback step and a pointer to the spec status. recipe-platform#30.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
feat(workflow) Add a status to specs and record plan deviations in the plan
All checks were successful
/ typecheck-contract (pull_request) Successful in 20s
6a74489773
Spec status (recipe-platform#26): every spec carries a status that follows
the gates: Spec, Phase A: Contract, Phase B: Repo architecture, Phase C:
Planning, Implementation, Review, Done. One status until GATE A, then one
line per affected repo. Changes after GATE A go through a status PR that
the user merges; the new shared skill recipe-workflow:spec-status owns that
procedure and asks when an earlier status PR is still open. The po agent,
plan-feature, implement-plan, implement-feature and review-feature set the
status at their steps. Epics get a coarse Status column.

Plan deviations (recipe-platform#33): every plan ends with an append-only
Deviations section. implement-plan appends an entry per deviation and
review-implementation treats listed deviations as agreed while checking
them against the code.

Each changed skill and agent has its ADR; two cross-cutting ADRs record
the conventions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
araemer changed title from feat(workflow) Lettered options for PO and architect; push every commit and keep one draft PR to feat(workflow) Spec status, plan deviations, lettered options, draft PRs per repo 2026-10-03 11:43:48 +00:00
docs(features) #001 Status: recipe-backend Done, recipe-app Done
All checks were successful
/ typecheck-contract (pull_request) Successful in 20s
6068c59aaf
Both feature PRs (recipe-backend#21, recipe-app#47) were merged into stage
on 2026-10-03. Spec A of E01 is Done in the epic's Status column.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
araemer/recipe-platform!34
No description provided.