Loading...
Loading...
Assess if IDD fits your project and learn about Intent-Driven Development. Use /intent-assess to evaluate project suitability or /intent-assess --learn for IDD education.
npx skill4agent add arcblock/idd intent-assess/intent-assess/intent-assess --learn/intent-assess
↓
┌───────────────────────────────────┐
│ Phase 1: Project Analysis │
│ - Project Type Identification │
│ - Codebase Scale │
│ - Existing Documentation Status │
│ - Team Collaboration Model │
└─────────────┬─────────────────────┘
↓
┌───────────────────────────────────┐
│ Phase 2: Suitability Assessment │
│ - Calculate Matching Score │
│ - Identify Strengths and Challenges │
└─────────────┬─────────────────────┘
↓
┌───────────────────────────────────┐
│ Phase 3: Recommendations │
│ - Recommend IDD or Not │
│ - How to Get Started │
│ - Alternatives (if Not Suitable) │
└───────────────────────────────────┘| Dimension | Favorable for IDD | Unfavorable for IDD |
|---|---|---|
| Project Type | System software, frameworks, libraries | Simple scripts, one-off projects |
| Code Scale | Medium to large (>5k LOC) | Small (<1k LOC) |
| Team Collaboration | Multi-person collaboration, AI-assisted | Individual independent development |
| Architecture Complexity | Multi-module, requires boundaries | Single-module, simple structure |
| Iteration Approach | Continuous iteration, long-term maintenance | One-time delivery |
| AI Tool Usage | Using Claude/Copilot | Manual-only development |
# IDD Assessment Report
> Project: ainecore
> Date: 2026-01-19
## Suitability Score: 85/100 ⭐⭐⭐⭐
## Project Characteristics
| Characteristic | Current Status | IDD Alignment |
|----------------|----------------|---------------|
| Project Type | Framework/Platform | ✅ High |
| Code Scale | ~15k LOC | ✅ High |
| Number of Modules | 12 | ✅ High |
| Team Size | 3 people + AI | ✅ High |
| Existing Documentation | Partial | 🟡 Medium |
## Strengths
- ✅ Multi-module architecture requires clear boundaries and contracts
- ✅ AI-assisted development can directly use Intent as context
- ✅ Long-term maintenance project, high documentation value
- ✅ Partial design documentation exists, which can be migrated
## Challenges
- ⚠️ Need to establish Intent writing habits
- ⚠️ Existing code needs Intent supplementation
- ⚠️ Team needs to learn IDD methods
## Recommendations
### Recommendation: Adopt IDD ✅
This project is highly suitable for IDD:
1. Multi-module architecture requires clear boundaries and contracts
2. AI-assisted development can directly use Intent as context
3. High long-term maintenance value
### Onboarding Recommendations
1. **Start with core modules**
- Write Intent for `src/core/` first
- Establish Intent templates and specifications
2. **Gradual promotion**
- New features must have Intent written first
- Gradually supplement Intent for old code
3. **Tool support**
- Install IDD plugin
- Configure CI/CD integration
### Expected Benefits
- 🎯 ~30% improvement in AI coding efficiency
- 🎯 Clearer architecture boundaries
- 🎯 Faster onboarding for new members
- 🎯 Reduced "outdated documentation" issues/intent-assess --learn┌───────────────────────────────────┐
│ Welcome to learning IDD! │
│ │
│ I will cover: │
│ 1. What is IDD │
│ 2. IDD vs TDD vs SDD │
│ 3. Intent File Structure │
│ 4. Practical Examples │
│ │
│ Which topic would you like to start with? │
└───────────────────────────────────┘Evolution of Development Methodologies:
Traditional: Code → Test → Docs
(Documentation often becomes outdated)
SDD: Spec → Code → Test
(Specs are scattered and hard to maintain)
TDD: Test → Code → Docs
(Tests cannot capture design rationale)
IDD: Intent → Test → Code → Sync
(Intent serves as the single source of truth)┌─────────────────────────────────────┐
│ Layer 1: Structure Diagram │
│ - Directory structure, data structure, module relationships │
│ - ASCII diagrams preferred │
├─────────────────────────────────────┤
│ Layer 2: Constraint Rules │
│ - Dependency direction, boundary rules, invariants │
│ - Convertible to test assertions │
├─────────────────────────────────────┤
│ Layer 3: Behavior Examples │
│ - Input → Output examples │
│ - Boundary cases │
└─────────────────────────────────────┘| Dimension | SDD | IDD |
|-----------|-----|-----|
| Organization | By type (function/UX/technology) | By module |
| Core Carrier | Text description | Structure diagram |
| Granularity | Granular User Stories | Complete Patterns |
| Task Management | Independent Task files | AI autonomous decomposition |
| LLM Friendliness | Context assembly required | Complete understanding in one go |/intent-assess --learn --topic <topic>whatvs-sddvs-tddstructureworkflowapprovalbest-practices/intent-assess # Assess project
↓ (if suitable)
/intent-assess --learn # Learn IDD
↓
/intent-init # Initialize IDD
↓
/intent-interview # Create Intent