Closing the intent-to-code chasm - specification-driven development with BDD verification chain
95
Does it follow best practices?
Validation for skill structure
Convert existing tasks into dependency-ordered GitHub issues for project tracking.
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty).
Run prerequisites check:
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-08-taskstoissues/scripts/bash/check-prerequisites.sh --phase 08 --jsonWindows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-08-taskstoissues/scripts/powershell/check-prerequisites.ps1 -Phase 08 -Json
Parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Extract path to tasks.md.
If JSON contains needs_selection: true: present the features array as a numbered table (name and stage columns). Follow the options presentation pattern in conversation-guide.md. After user selects, run:
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-08-taskstoissues/scripts/bash/set-active-feature.sh --json <selection>Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-08-taskstoissues/scripts/powershell/set-active-feature.ps1 -Json <selection>
Then re-run the prerequisites check from step 1.
git config --get remote.origin.urlCRITICAL: Only proceed if remote is a GitHub URL (git@github.com: or https://github.com/). Otherwise ERROR.
Extract: Task IDs, descriptions, phase groupings, parallel markers [P], user story labels [USn], dependencies.
Title format: [FeatureID/TaskID] [Story] Description — feature-id extracted from FEATURE_DIR (e.g. 001-user-auth).
Body: use template from issue-body-template.md. Labels (create if needed): iikit, phase-N, us-N, parallel.
Use the Task tool to dispatch issue creation in parallel — one subagent per chunk of tasks (split by phase or user story). Each subagent receives:
gh issue create if available, otherwise curl the GitHub API# Preferred:
gh issue create --title "[001-user-auth/T012] [US1] Create User model" --body "..." --label "iikit,phase-3,us-1"CRITICAL: Never create issues in repositories that don't match the remote URL. Verify before dispatching.
Collect all created issue numbers from subagents. Verify all returned successfully before proceeding. If some failed: report failures, continue with successful issues only.
After all issues exist, edit bodies to add cross-references using #NNN syntax. Skip dependency links for any issues that failed to create.
Output: issues created (count + numbers), failures (count + details), link to repo issues list.
| Condition | Response |
|---|---|
| Not a GitHub remote | STOP with error |
| Issue creation fails | Report, continue with remaining issues |
| Partial failure | Link dependencies for successful issues only |
Run: bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-08-taskstoissues/scripts/bash/next-step.sh --phase 08 --json
Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-08-taskstoissues/scripts/powershell/next-step.ps1 -Phase 08 -Json
Parse the JSON and present:
next_step will be null (workflow complete)alt_steps non-empty: list as alternativesIf on a feature branch, offer to merge:
git checkout main && git merge <branch>gh pr createFormat:
Issues exported! Review in GitHub, assign team members, add to project boards.
- Dashboard: file://$(pwd)/.specify/dashboard.html (resolve the path)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