Closing the intent-to-code chasm - specification-driven development with BDD verification chain
86
92%
Does it follow best practices?
Impact
86%
1.82xAverage score across 14 eval scenarios
Advisory
Suggest reviewing before use
Used by Step 6 (Seed backlog from PRD) when creating GitHub issues from extracted features.
Create before issues (idempotent). Use gh if available, otherwise curl the GitHub API.
# Preferred:
gh label create feature --description "Feature extracted from PRD" --color 0E8A16 --force
gh label create iikit --description "Intent Integrity Kit" --color 1D76DB --forceUse gh if available, otherwise curl the GitHub API (POST /repos/{owner}/{repo}/issues).
# Preferred:
gh issue create --title "<feature title>" --body "<body>" --label "iikit,feature"## Feature
<description>
## Priority
<P1/P2/P3>
## Source
Extracted from PRD: `<filename or URL>`
## Next Steps
Run `/iikit-01-specify #<this-issue>` to create a full specification.
---
*Seeded by /iikit-core init*evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
rules
skills
iikit-00-constitution
scripts
dashboard
iikit-01-specify
iikit-02-plan
iikit-03-checklist
scripts
bash
dashboard
iikit-04-testify
iikit-05-tasks
iikit-06-analyze
iikit-07-implement
iikit-08-taskstoissues
iikit-bugfix
scripts
dashboard
iikit-clarify
iikit-core
references
scripts
bash
dashboard
powershell
templates