Menu
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
Expert-level Atomic Design System development from Figma style guides. Build reusable component libraries with atoms, molecules, organisms, templates, and pages.
| name | aid-discovery |
| description | AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed. |
Purpose: Validate problem space before committing to solution.
Entry: Initial idea/request exists, stakeholders available Exit: Problem validated, stakeholders identified, success metrics defined, go/no-go decision
## Problem Statement
### Situation
[Current state]
### Complication
[What's wrong]
### Question
[What solving this answers]
### Impact
- [Quantified impact]
### Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| [Metric] | [Now] | [Goal] |
### Decision Makers
- [Name/Role]: [Responsibility]
### Data/System Owners
- [Name/Role]: [What they own]
### End Users
- [Type]: [How affected]
### Integrations
- [System]: [Relationship]
| Pitfall | Fix |
|---|---|
| Solution-first | Start with "what problem?" |
| Missing stakeholders | Ask "who else touches this?" |
| Vague problems | If can't measure, not defined |
| Assumption blindness | Make assumptions explicit |