Closing the intent-to-code chasm - specification-driven development with BDD verification chain
95
Does it follow best practices?
Validation for skill structure
Used by taskstoissues when creating GitHub issues from tasks.
## Task Details
**Task ID**: <feature-id>/<task-id>
**Phase**: <phase name>
**User Story**: <USn>
**Parallel**: Yes/No
## Description
<task description>
## Dependencies
- Depends on: <linked issues>
- Blocks: <linked issues>
## Acceptance Criteria
- [ ] File created at specified path
- [ ] Tests pass (if applicable)
---
*Generated by /iikit-08-taskstoissues*Install with Tessl CLI
npx tessl i tessl-labs/intent-integrity-kit@2.7.12rules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-plan
iikit-03-checklist
scripts
dashboard
iikit-04-testify
iikit-05-tasks
iikit-06-analyze
iikit-07-implement
iikit-08-taskstoissues
iikit-bugfix
scripts
dashboard
iikit-clarify
iikit-core
scripts
bash
dashboard
powershell
templates