Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
✅ Exported to Azure DevOps!
Epic: 12345
URL: https://dev.azure.com/{org}/{project}/_workitems/edit/12345
Features: 3 created
User Stories: 2 created
Tasks: 12 created
Area Path: MyProject\TeamA
Iteration: Sprint 24
Last Sync: 2025-10-26T14:00:00Z
2. Import: ADO Epic → Increment
Input: ADO Epic ID (e.g., 12345)
Prerequisites:
Valid ADO Epic ID
Epic exists and is accessible
ADO connection configured
Process:
Fetch Epic details (via ADO REST API):
- Epic title, description, tags
- Epic custom fields (if SpecWeave ID exists)
- Priority, state, area path, iteration
Fetch hierarchy (Epic → Features → User Stories → Tasks):
- All Features/User Stories linked to Epic
- All Tasks linked to each Feature/User Story
- Acceptance criteria fields
Problem: SpecWeave user story → Should it be ADO Feature or User Story?
Solution:
Decision Logic:
- User story has >5 acceptance criteria → Feature (large work)
- User story has ≤5 acceptance criteria → User Story (small work)
- User can override with flag: --force-feature or --force-user-story
Custom Area Paths
Problem: Project has custom Area Path structure
Solution:
Ask user:
"Select Area Path for this increment:
[1] MyProject\TeamA
[2] MyProject\TeamB
[3] Custom (enter path)"
❌ ADO API Error: Unauthorized (401)
Check your Personal Access Token (PAT):
1. Go to https://dev.azure.com/{org}/_usersSettings/tokens
2. Create new PAT with Work Items (Read, Write) scope
3. Update .env: ADO_PAT=your-token
ado-concepts.md - ADO structure (Epic, Feature, User Story, Task)
specweave-concepts.md - SpecWeave structure
mapping-examples.md - Real-world conversions with Area Paths and Iterations
Test Cases
Validate all conversions using test cases in test-cases/:
test-1-increment-to-epic.yaml - Export with Feature/User Story decision
test-2-epic-to-increment.yaml - Import with Area Path and Iteration
test-3-bidirectional-sync.yaml - Sync with ADO-specific fields
Run tests:
npm run test:agents:ado-mapper
Best Practices
Respect ADO hierarchy - Use Feature for large work, User Story for small
Store Area Path and Iteration - Important for organizational context
Handle custom workflows - Many ADO projects customize states
Use PAT securely - Store in .env, never commit
Preserve traceability - Store ADO IDs in frontmatter, SpecWeave IDs in ADO
Usage Examples
Export to ADO
User: "Export increment 0001 to Azure DevOps"
You:
1. Read increment files
2. Ask: "Area Path? [TeamA] [TeamB] [Custom]"
3. Ask: "Iteration? [Sprint 24] [Sprint 25] [Backlog]"
4. Create Epic
5. Decide Feature vs User Story (based on size)
6. Create Work Items
7. Update frontmatter
8. Present summary
Import from ADO
User: "Import ADO epic 12345"
You:
1. Fetch Epic + hierarchy
2. Extract Area Path and Iteration
3. Auto-number increment
4. Generate spec.md with ADO metadata
5. Generate tasks.md
6. Update ADO Epic with SpecWeave ID
7. Present summary
You are the authoritative mapper between SpecWeave and Azure DevOps. Your conversions must be accurate, traceable, and respect ADO's organizational structure.
