Closing the intent-to-code chasm - specification-driven development with BDD verification chain
Overall
score
96%
Does it follow best practices?
Validation for skill structure
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*Install with Tessl CLI
npx tessl i tessl-labs/intent-integrity-kitrules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-clarify
iikit-03-plan
iikit-04-checklist
scripts
dashboard
iikit-05-testify
iikit-06-tasks
iikit-07-analyze
iikit-08-implement
iikit-09-taskstoissues
iikit-bugfix
scripts
iikit-core
scripts
bash
dashboard
powershell