feat(ce-brainstorm): product-tier with end-to-end ID traceability#629
Merged
Conversation
Deep brainstorms now split into feature (inherits product shape) and product (must establish it). Product-tier adds triggered Actors, Key Flows, and Acceptance Examples sections with A/F/AE IDs that ce-plan carries forward and ce-work references in blockers and verification — traceability runs end to end.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 73202cdbd1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Phase 1.2 product-tier guidance referenced a "Positioning subsection" that doesn't exist in requirements-capture.md. The final design uses Scope Boundaries split into "Deferred for later" and "Outside this product's identity". Update the reference to match. Address PR review feedback (#629)
tmchow
changed the title
Merged
tmchow
added a commit
that referenced
this pull request
Apr 21, 2026
Mirror the ce-brainstorm requirements-capture.md legibility convention: horizontal rules (---) between top-level sections in Standard and Deep plans. Improves scannability of dense plans where many H2 sections sit close together. Omit for Lightweight plans. Adds the convention to Phase 4.3 Planning Rules and inserts separators throughout the core template and the optional Deep-extension template. Refs PR #629 (originated the convention in the brainstorm template).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brainstorming greenfield work in
ce-brainstormpreviously had thin guidance and no structural support — the requirements template was optimized for incremental changes inside an existing product. Deep-scope brainstorms now split into feature-tier (inherits product shape) and product-tier (must establish it), with triggered sections for Actors, Key Flows, and Acceptance Examples carrying stable IDs that preserve product intent through planning and execution.What changes
ce-brainstorm— Phase 0.3 classifies Deep work as either Deep-feature (default, current behavior) or Deep-product based on whether product shape must be established. Phase 1.2 adds three product-tier pressure-test questions that force an explicit product thesis. Phase 2 clarifies that product-tier alternatives should differ on what is built, not how.requirements-capture.md— Restructured around a tier-by-section matrix. Three new triggered sections:A-IDs) — included when multiple humans, agents, or systems are meaningfully involved. Covers both end-user actors for product work and pipeline-agent actors for agent-workflow work.F-IDs) — 2-4 primary flows expected by default at product tier, optional elsewhere. Each flow has trigger, actors, steps, outcome, and aCovered by: R-IDsback-reference so cross-cutting behavior survives into planning.AE-IDs) — included when a requirement's behavior is hard to pin down without a concrete scenario. Each example disambiguates viaCovers: R-IDs. Definitive for what's listed, not exhaustive.At product tier, Scope Boundaries splits into "Deferred for later" vs "Outside this product's identity" — the first is sequencing, the second is identity.
ce-plan— Origin-document carry-forward now explicitly preserves A/F/AE IDs as constraints implementation units must honor, and handles the Scope Boundaries split.ce-work,ce-work-beta— Progress tracking references R-IDs (and optionally A/F/AE IDs) in blockers, deferred-work notes, task summaries, and final verification — not routine status updates. Closes the traceability loop from requirements to execution.Section matrix at a glance
Non-triggered sections (Problem Frame, Requirements with R-IDs, Success Criteria, Key Decisions, Dependencies / Assumptions, Outstanding Questions, Next Steps) are unchanged.
Design notes
ce-brainstorm's existing scope classification so users don't pre-commit to a workflow type.ce-work-betasynced withce-work— the R-ID traceability guidance applies equally to both execution modes.Test plan
Skill-content change, no test-suite changes required. Verified:
bun test— 831 passing, 0 failing.bun run release:validate— clean (50 agents, 45 skills).