Pre-flight Checks
Problem Description
When users express vague intents like 'I want to add some kind of way for the audience to participate more', SDD jumps directly to explore or propose. The LLM invents users, constraints, and scope without user input, leading to misaligned proposals that require heavy correction later.
Proposed Solution
Add IDD (Idea-Driven Development) as a pre-SDD discovery phase:
- IDD Clarity Check: automatically intercepts underdefined intents before sdd-explore/sdd-propose
- IDD Session Preflight: clarity level + discovery depth + artifact store
- Interactive discovery loop: domain-focused questions, one at a time, using the question tool with selectable options
- Intent artifact: rigid schema with goal, reason, users, domain entities, constraints, decisions, open questions, ready assessment
- Non-code gate: blocks non-software solutions (process changes, SaaS purchases) with a clear recommendation
- Deep depth delegation: dedicated idd-discover sub-agent for complex intents requiring decision ledger
- SDD integration: sdd-propose reads intent artifacts and skips proposal question round when confidence is medium or higher; sdd-explore supports focused impact analysis mode
Coverage: all 12 orchestrator platforms. Sub-agent definitions for opencode, cursor, claude, kiro, kimi.
Affected Area
Skills (idd-discover, sdd-propose, sdd-explore), Commands, Orchestrator instructions (12 variants), Go source (profiles, catalog, inject, commands), OpenCode overlay JSONs
Alternatives Considered
Inline-only discovery without a dedicated skill: rejected because deep discovery needs a sub-agent for fresh context and decision ledger persistence.
Additional Context
- Branch: feat/idd-discovery-harness (commit a4d00a7)
- Size: ~1353 lines across 29 files
- Judgment Day: 2 rounds, 21 findings reviewed, 0 CRITICAL remaining
- Tested live: IDD Clarity Check triggered automatically on vague intent
Pre-flight Checks
Problem Description
When users express vague intents like 'I want to add some kind of way for the audience to participate more', SDD jumps directly to explore or propose. The LLM invents users, constraints, and scope without user input, leading to misaligned proposals that require heavy correction later.
Proposed Solution
Add IDD (Idea-Driven Development) as a pre-SDD discovery phase:
Coverage: all 12 orchestrator platforms. Sub-agent definitions for opencode, cursor, claude, kiro, kimi.
Affected Area
Skills (idd-discover, sdd-propose, sdd-explore), Commands, Orchestrator instructions (12 variants), Go source (profiles, catalog, inject, commands), OpenCode overlay JSONs
Alternatives Considered
Inline-only discovery without a dedicated skill: rejected because deep discovery needs a sub-agent for fresh context and decision ledger persistence.
Additional Context