Trevin Chow 8dda3ad18f feat: add optional high-level technical design to ce:plan-beta and deepen-plan-beta ...

User feedback indicated that seeing pseudo-code, DSL grammars, or
architectural diagrams in plans helps reviewers validate the approach
direction — without crossing into prescriptive implementation code that
downstream agents take as gospel.

Changes to ce-plan-beta:
- Soften "decisions, not code" principle to allow pseudo-code/DSL sketches
  framed as directional guidance
- Add Phase 3.4 "High-Level Technical Design" with a decision table for
  choosing the right medium (pseudo-code, mermaid, data flow, state diagram)
- Add optional per-unit "Technical design" field for unit-level sketches
- Update template with the new optional section and non-prescriptive framing
- Clarify Standard/Deep depth guidance that optional sections should be
  omitted when they add no value

Changes to deepen-plan-beta:
- Add confidence gap checklists for technical design (when present and absent)
- Add agent mapping for validating/strengthening technical design sections
- Expand allowed changes to cover both top-level and per-unit technical design
- Align guardrails to explicitly permit pseudo-code in both locations

2026-03-19 22:01:29 -07:00

..

coding-tutor

Remove cursor target and add plugin metadata

2026-02-13 12:14:48 -05:00

compound-engineering

feat: add optional high-level technical design to ce:plan-beta and deepen-plan-beta

2026-03-19 22:01:29 -07:00