| name | sdd-4b-didyouknow |
| description | Build shared understanding by surfacing non-obvious insights from SDD artifacts. Use when: before complex implementation, after creating a spec or plan, when feeling uncertain about assumptions, or between the Architect and Implement phases. |
SDD Phase 4b: Did You Know?
Surface non-obvious insights from SDD artifacts to build shared understanding before implementation. Presents insights one at a time and immediately updates the relevant artifact after each discussion.
Inputs
- slug (Optional): Slug from prior phases. Inferred from context if omitted.
- artifact (Optional): Which artifact to analyze:
spec, plan, or tasks. If omitted, auto-detect the most recent relevant artifact.
Step 0: Doctrine Resolution
Before starting, resolve project conventions:
- Check for project doctrine files:
docs/project-rules/ (constitution.md, rules.md, idioms.md, architecture.md)
copilot-instructions.md, AGENTS.md, CONTRIBUTING.md, README.md
- If no doctrine found, scan the codebase for dependency manifests, build systems, and directory patterns.
- Extract: build command, test command, coverage threshold, naming conventions, CI platform.
- Unknown values become explicit
[TODO] markers — never assume silently.
Step 1: Load Artifact Context
- Determine which artifact to analyze based on
{artifact} or auto-detection:
spec → .copilot-tracking/plans/{date}/{slug}/{slug}-spec.md
plan →