Skip to content

Latest commit

 

History

History
207 lines (151 loc) · 28.7 KB

CHANGELOG.md

File metadata and controls

207 lines (151 loc) · 28.7 KB

Changelog

Unreleased

Bug Fixes

  • iikit-bugfix, iikit-08-taskstoissues, iikit-07-implement no longer prescribe a URL-fetch surface: v2.10.13 still failed Snyk moderation after PR #93 cleaned only PRD-seeding. The remaining triggers were curl GitHub API instructions and literal https://github.com/ example URLs across these three skills. All three now describe issue/PR/comment operations tool-agnostically ("whichever tool is available"); capability unchanged. Source-tests test_github_fallback reframed accordingly.
  • PRD-seeding instructions no longer prescribe a URL-fetch surface: Follow-up to #91 — the consent docs in v2.10.12 cleared W012 and one W011 but left E005 and one W011 standing. iikit-core/SKILL.md and prd-seeding.md now describe the input in tool-agnostic terms ("the document the user named"); the capability is unchanged.
  • CI: temporarily pin E2E tessl install to @2.10.9: v2.10.10 and v2.10.11 failed Tessl's Snyk-backed moderation with a Critical security score, so tessl install tessl-labs/intent-integrity-kit (which resolves latest) hits the install-policy block on every PR's CI run. The publish job in ci.yml is needs: [test, test-windows], so the failing test job also skipped publish — a deadlock that prevented any new version (including the moderation fix in f81d53e) from reaching the registry. Pin the three E2E install commands in ci.yml to @2.10.9 --accept-warnings (the last version that passed moderation with Advisory-only findings) so test passes, publish fires, and the moderation fix lands as v2.10.12. Follow-up PR will revert the pin once v2.10.12 re-scores below Critical.
  • Document PRD-seeding consent model; remove literal example URL from skill instructions: Tessl's Snyk-backed moderation flagged v2.10.10/v2.10.11 Critical with E005 (suspicious download URL), W011×2 (third-party content exposure / indirect prompt injection), and W012 (runtime URL controls agent), citing the /iikit-core init <PRD-url> flow. The behavior is intentional — user-opt-in only, gated behind explicit input — but was undocumented and used a literal https://example.com/prd.md placeholder that tripped the URL-pattern check. iikit-core/references/prd-seeding.md now opens with a "Security and consent model" section explaining the opt-in surface, the artifact-review gate (PREMISE.md → /iikit-00-constitution), and the no-code-execution boundary; iikit-core/SKILL.md's argument-parsing paragraph replaces the literal URL with a <PRD-url> placeholder and links the consent model. Agentic moderation should re-score against the explicit consent narrative.
  • Verify tile step retries through moderation gate: Tessl 0.81+ returns 403 Forbidden on tessl install while a just-published version's moderationStatus is pending. The publish job's verify step ran the install immediately after publish, hit the 403, fell through to a dead @0.7.0/@0.6.5 fallback, and cascaded 73 "skill directory missing" failures. tests/run-tile-tests.sh now retries the registry install with exponential backoff between attempts (30 → 60 → 120 → 240 → 300 → 300 seconds, 7 attempts total, ~17.5 min budget) and fails cleanly with admin-override remediation guidance if it never clears. Dead version-fallback removed.
  • Tessl install path moved from .tessl/tiles/ to .tessl/plugins/ (#80): Tessl CLI 0.81+ installs tiles to .tessl/plugins/<workspace>/<tile>/ instead of .tessl/tiles/<workspace>/<tile>/. Every hardcoded reference in the repo (CI workflows, gh-aw policy-reviewer prompts, every iikit-*/SKILL.md invoking a script, pre/post-commit hooks, dev-time symlink, source/tile test paths) was updated to the new path. Without this fix, CI's E2E install test fails on every PR, the OpenAI gh-aw reviewer posts Policy load failed CHANGES_REQUESTED on every PR, and end-users on Tessl 0.81+ get "No such file or directory" when invoking any iikit skill. Mechanical rename only — no behavior change.

Features

  • argument-hint: frontmatter on argument-taking skills (#75): The five iikit skills that accept arguments — iikit-core, iikit-01-specify, iikit-bugfix, iikit-08-taskstoissues, iikit-clarify — now carry an argument-hint: frontmatter field. Claude Code's slash-command UI surfaces the hint inline so users see the expected input shape without reading the SKILL body. Harvested from upstream spec-kit commit 10be4848 (PRs #2059, #1951). No runtime cost; other agents ignore the unknown field per rule-frontmatter passthrough.
  • --paths-only works on non-feature branches; --dry-run for create-new-feature (#76): check-prerequisites.sh --paths-only (and its equivalent --phase core) now emits paths without the feature-branch gate — useful for CI dry-runs, worktree-isolated read-only inspection, and feeding the planned /iikit-core doctor (#74) with structured path data. PowerShell mirror updated. create-new-feature.sh --dry-run (and -DryRun in PowerShell) previews BRANCH_NAME / FEATURE_NUM / SPEC_FILE without creating the git branch, the specs/NNN-*/ directory, or spec.md. JSON output carries "dry_run": true. Harvested from upstream spec-kit commits 3227b966 (#2672) and b44ffc01 (#1998).
  • Gitflow branch prefixes in feature detection (#77): The active-feature cascade now recognizes both NNN-name (standard) and <prefix>/NNN-name (gitflow, e.g. feat/001-user-auth, fix/042-null-deref). New extract_feature_id / Get-FeatureIdFromBranch helper strips the prefix; get_current_branch, check_feature_branch, find_feature_dir_by_prefix, and the create-new-feature.sh highest-number scan all route through it. Teams on gitflow conventions no longer fall through to "single feature auto-select" or hit an error. Cascade semantics unchanged. Harvested from upstream spec-kit commit 4687c33b (PR #2202).
  • Canonical ## Step N — Title headings across all iikit skills (#86): Every iikit-*/SKILL.md now uses the flat ## Step N — Descriptive Title form mandated by jbaruch/coding-policy: skill-authoring. Each skill has the appropriate execution-mode preamble after its H1 (sequential workflows get Process steps in order. Do not skip ahead.; iikit-core gets the action-router preamble). Parent ## Execution Flow / ## Execution Steps headings removed. Sub-step decimals flattened: iikit-04-testify's #### 2.1/2.2 reference sections become bold labels under Step 2; iikit-06-analyze's ### 5b promoted to its own Step 6 (existing 6, 7 renumbered to 7, 8); iikit-07-implement's ### 2.1–2.4 constraints absorbed into Step 3 body and the existing 3→6 numbering gap closed (now Steps 1–9); iikit-bugfix's ### 2a/2b branches merged into one Step 2 with bold branch labels. iikit-00-constitution's numbered list under ## Execution Flow converted to 10 flat Step headings. iikit-core restructured: each subcommand (init, status, use, uninit, help) now lives under its own ## Step N — name heading with internal procedure as numbered list bullets in the body. No behavior change; affects 88 step headings across 12 skills.
  • Re-validate checklists after /iikit-clarify (#73): When the clarified target is spec.md and one or more checklists/*.md files are present, the skill now re-evaluates each item against the updated spec — unchecking items invalidated by the clarification ([Stale] tag with one-line note), checking off [Gap] items the clarification resolves, and writing a regressions/resolved/unchanged diff into the spec's ## Clarifications session. Non-spec targets (plan, tasks, testify, checklist, constitution) skip the step. Closes the stale-state hole where a clarification could leave a previously-green checklist out of sync with the spec it scored. Harvested from upstream spec-kit PR #2715.
  • Linked-worktree / submodule hook install (#67): /iikit-core init and /iikit-core uninit now resolve the hooks directory via git rev-parse --git-path hooks instead of assuming $PROJECT_ROOT/.git/hooks. Running init/uninit from a linked worktree or submodule (where .git is a file pointing at the real gitdir) now lands hooks in — and removes them from — the actual gitdir's hooks/ directory (the main repo's .git/hooks/ for worktrees, .git/modules/<name>/hooks/ for submodules), matching the place git invokes hooks from. install_hook / Install-IIKitHook and the pre-commit.d/ extension point share a single resolved path so they stay in lockstep across every layout. Repo detection switched from -d .git / Test-Path .git to git rev-parse --is-inside-work-tree. JSON contract unchanged; the human-readable status line for pre-commit.d/ now prints the resolved path so worktree users see where the extension dir actually lives. BATS + Pester coverage for both checkouts and worktree-initiated runs.
  • pre-commit.d/ extension point (#61): IIKit's pre-commit hook now executes every executable in .git/hooks/pre-commit.d/ before its own assertion-integrity check — IIKit remains the final gate, so any extension-side mutation of .feature / test-specs.md / context.json (formatter reflow or hostile tampering) is caught against the post-extension staged state. Extensions run in LC_ALL=C byte order; if one fails the rest in the dir still run but the hook exits non-zero after the loop and IIKit does not run. Extensions are skipped only when no git repo is detected. /iikit-core init provisions the directory with a discoverable README (marked IIKIT-PRE-COMMIT-D) explaining the convention. /iikit-core uninit removes that README and drops the dir when empty, reporting any remaining entries (scripts, dotfiles, subdirs, non-iikit READMEs) as preserved user content. Lets downstream projects layer prettier/eslint/secret-scan checks without touching .git/hooks/pre-commit (which IIKit still owns) — the previous workaround relied on hook managers renaming the IIKit hook to pre-commit.old, which the assertion-integrity rule forbids. Assertion-integrity rule now points at the new extension point and explicitly bars hook managers that overwrite/rename .git/hooks/pre-commit. Reference doc at .claude/skills/iikit-core/references/hook-chaining.md with examples. BATS + Pester coverage.
  • /iikit-core uninit subcommand (#62): New action that removes iikit-managed scaffolding (.git/hooks/pre-commit/post-commit IIKit blocks, alongside iikit-* hooks, chain-call lines in user hooks, .specify/, TECH.md when it carries an iikit phase reference) and reports user-authored content (CONSTITUTION.md, PREMISE.md, specs/) so the user decides. Run it BEFORE tessl uninstall tessl-labs/intent-integrity-kit to avoid orphaned hooks and stale tile artifacts. Supports --dry-run and --remove-user-content. BATS + Pester coverage.

Bug Fixes

  • Symlinked tests/features/ not traversed by find (#59): Every find over .feature files in iikit-core scripts (check-prerequisites.sh, pre-commit-hook.sh, bugfix-helpers.sh, verify-assertion-integrity.sh, verify-steps.sh) now passes -L so a symlinked tests/features/ directory (e.g., Maven layout where it points to src/test/resources/features/) is followed. Previously the testify gate falsely reported "features": false and blocked phases 05–08 even when .feature files existed.

Documentation

  • Caveman companion recommendation (#46): README "Recommended Companion" section and /iikit-core init Step 5 now point users to juliusbrussee/caveman. A 4-demo × 2-arm benchmark measured ~30% cost and wall-clock reduction across the full IIKit workflow with FR coverage preserved. Issue #46 remains open for deeper input-compression work on IIKit's own SKILL.md files.

v2.10.0

Bug Fixes

  • Dashboard replace corruption (#49): String.prototype.replace() in generate-dashboard.js now uses function callbacks to prevent $-pattern corruption ($', ``$```, $$, `$&`) in spec/task content.
  • Branch detection cascade (#44, #45): get_current_branch() now prioritizes the git branch over the stale .specify/active-feature file when on a feature branch (NNN-*). Fixes wrong feature detection after switching branches.
  • Pre-commit step definitions gate (#48): Gate 1 now checks both working tree and git staging area (--diff-filter=ACMR) for step definition files, preventing false warnings during /iikit-07-implement.
  • Dashboard clarification panels (#39): Clarification badges are now clickable — pointer-events: auto with addEventListener navigates to the clarify view panel. Added aria-label for accessibility.

Features

  • GitHub Copilot support (#40): Added .github/copilot-instructions.md symlink to AGENTS.md, updated setup scripts (Unix + Windows) with cross-directory symlink support, added copilot case to update-agent-context.
  • Assertion integrity enforcement (#55): Defense-in-depth against pre-commit hook bypass:
    • verify-assertion-integrity.sh — CI-callable server-side hash verification (agent-agnostic, works in any CI)
    • check-hook-bypass.sh — Claude Code PreToolUse hook blocking --no-verify, hook deletion, and git plumbing bypass
    • Constitution template — new "Pre-Commit Hook Enforcement (NON-NEGOTIABLE)" section
    • Assertion integrity rules — explicit bypass prohibitions added
    • Pre-commit hook output no longer suggests --no-verify as bypass path

Closed Without Code Change

  • #38: Dashboard health score parser/analyze mismatch — already fixed in current code.
  • #43: --version exit code null — Tessl CLI bug, not IIKit.

v2.9.0

  • Commit strategy choice: /iikit-07-implement asks users to choose between per-task commits (bisectable history, default) or batch commits (per-phase, ~47% faster). Batch mode cuts implementation from ~58 turns to ~31 turns.
  • Unified post-phase.sh: New script combines commit + dashboard refresh + next-step into a single tool call. All 9 artifact-producing skills updated. Eliminates 2 redundant tool call round-trips per phase.
  • Dashboard deduplication: check-prerequisites.sh no longer generates the dashboard — was causing double dashboard generation per phase.
  • Performance profiling: End-to-end pipeline profiled (init through implement). Implementation identified as 25% of total time, with 70-83% of each phase spent on ceremony vs productive work.

v2.8.0

  • 14 eval scenarios: 9 new cross-phase and full-pipeline evals. Baseline 48% → with context 88%.
  • Skill compliance fixes: Constitution context.json creation, plan spec quality gate, bugfix TDD fallback.
  • Eval anti-bleeding: Task.md files stripped of narrator coaching.

v2.7.13

  • Premise card grid: Constitution tab shows premise as a responsive card grid with click-to-expand.
  • Dashboard empty state: Shows premise + constitution immediately instead of infinite spinner when no features exist.
  • Architecture diagram fix: Parser matches flexible heading names (## Architecture, ## Architecture Overview, etc.). Node classifications from context.json instead of dead LLM API call.
  • Analyze parser: Handles bold sub-section headings, 5-column coverage table, flexible metric key names, and constitution alignment column detection by content.
  • Tile review scores: Color-coded eval and review score badges on plan view tile cards.
  • Testify clarifications: Clarify writes Q&A to tests/clarifications.md (Gherkin can't hold markdown). Tasks Q&A shown on implement node.
  • Checklist gating: requirements.md gated on checklist_reviewed_at in context.json. Checklist skill reviews existing file instead of creating duplicates.
  • Commit after every phase: All artifact-producing skills now commit before dashboard refresh.
  • Dashboard after artifacts: Generation moved after work in constitution, specify, plan, and bugfix skills.
  • Bash 3.2 compatibility: Pre-commit and post-commit hooks use sort -u instead of declare -A.
  • Bug cross-links: FR/SC/TS/T references in bug descriptions auto-link. Description column no longer truncates.

v2.7.5

  • 27 bug fixes from E2E testing across 12 projects (101 phases, 596 unit tests, 32 integration tests — all green).
  • Clarification badge fix: Badges now count - Q: items (not session headings), and track clarifications on checklist, analyze, and tasks phases (were hardcoded to 0).
  • Dashboard resilience: Generates without CONSTITUTION.md (was hard-fail exit 3), handles ESM projects with type:module.
  • Testified stage: New testified feature stage between planned and tasks-ready when .feature files exist but no tasks.md.
  • Pre-commit softened: Missing step_definitions and BDD runner dependency are now warnings, not commit blockers.

v2.7.1

v2.7.0

v2.6.0

  • Externalized next-step state machine: New next-step.sh / next-step.ps1 scripts serve as the single source of truth for all workflow transitions. All 12 SKILL.md files, check-prerequisites.sh status mode, and both session hooks (session-context-hook.sh, session-context-hook-gemini.sh) now delegate to this script instead of maintaining independent next-step logic.
  • Mandatory/optional path clarity: Mandatory path: 00→01→02→[04 if TDD]→05→07. Steps 03 (checklist), 06 (analyze), and 08 (tasks-to-issues) are optional and presented as alt_steps in JSON output.
  • Model tier in status output: check-prerequisites.sh --phase status --json now includes a model_tier field, codified from model-recommendations.md (light/medium/heavy).
  • Clear recommendations: Each transition includes clear_before and clear_after flags based on context consumption patterns (e.g., plan/implement consume heavy context → suggest /clear after).
  • Comprehensive test coverage: 56 new BATS tests for next-step.sh covering all phase transitions, TDD branching, artifact-state fallback, clear logic, model tiers, and alt steps. Pester tests for PowerShell parity.
  • Packaging transitive dependencies: prepare-tile.sh updated to ensure next-step.sh/ps1 are distributed as transitive deps when check-prerequisites.sh or session hooks are present.

v2.5.1

  • Clarify next-step fix: Clarify now uses feature state to determine the correct next-step suggestion instead of hardcoded phase logic.

v2.5.0

  • Generic clarify utility: /iikit-clarify extracted from the numbered sequence into a standalone utility. Can run after any phase on any artifact (spec, plan, checklist, testify, tasks, or constitution). Auto-detects the most recent artifact in reverse phase order; user can override with an argument (e.g., /iikit-clarify plan). Per-artifact ambiguity taxonomies: spec (functional scope, domain, UX, non-functional, edge cases, terminology), plan (framework choice, architecture, trade-offs, scalability, dependency risks), checklist (threshold appropriateness, missing checks, false positives), testify (scenario precision, missing paths, Given/When/Then completeness), tasks (dependency correctness, ordering, scope, parallelization), constitution (principle clarity, threshold specificity, conflict resolution, enforcement gaps).
  • Full skill renumbering: All downstream skills renumbered after extracting clarify. New sequence: iikit-02-plan, iikit-03-checklist, iikit-04-testify, iikit-05-tasks, iikit-06-analyze, iikit-07-implement, iikit-08-taskstoissues. Utilities: iikit-core, iikit-clarify, iikit-bugfix.
  • Dashboard clarification badges: Pipeline nodes display ?N amber badges when clarification sessions exist for that artifact's ## Clarifications section. Clarify removed from pipeline as a phase node. New countClarificationSessions() parser function counts ### Session YYYY-MM-DD headings per artifact.
  • Relaxed clarify prerequisites: check-prerequisites.sh --phase clarify no longer requires a feature directory or spec — can clarify a constitution alone. Phase config: soft constitution, no spec/plan/tasks requirements.
  • Checklist excludes requirements.md: parseChecklists() and parseChecklistsDetailed() now filter out requirements.md (spec quality checklist from /iikit-01-specify) to prevent falsely marking the checklist phase as complete before /iikit-03-checklist is actually run.

v2.4.0

  • BDD in bugfix workflow: When the constitution mandates TDD/BDD, /iikit-bugfix creates bugfix_BUG-NNN.feature files with Gherkin scenarios and re-hashes the features directory. /iikit-07-implement bugfix mode applies the full BDD verification chain when .feature files are present.
  • Testify enforcement across phases: check-prerequisites.sh gates phases 05-08 on .feature file existence when TDD/BDD is mandatory. All four defense lines (skill, rule, script, hook) now enforce testify.
  • Cached TDD determination: Constitution skill writes tdd_determination to .specify/context.json on ratification. All consumers read from cache instead of re-parsing the constitution.
  • BDD/behavior-driven detection: Constitution scanner recognizes BDD, behavior-driven, and behaviour-driven as synonyms for TDD.
  • Dashboard refresh rule: Always-on rule ensures dashboard regeneration after any file change in specs/ or project root. Skills also regenerate explicitly (testify, tasks, checklist, analyze).
  • Phase separation rule: Always-on rule enforcing no tech in constitution, no implementation in spec, no governance in plan.

v2.3.0

  • Always-on Tessl rules: Three alwaysApply: true rules loaded into agent context on every request — assertion-integrity (never tamper with .feature files or test assertions), phase-discipline (never code without spec/plan/tasks, never skip phases), and constitution (never violate CONSTITUTION.md principles). Adds a new defense-in-depth layer alongside skills, scripts, and git hooks.

v2.2.0

  • Pre-commit BDD runner enforcement: When .feature files exist, code commits are now mechanically gated on three checks: step definitions present, BDD runner dependency in project dep files, and verify-steps.sh dry-run passes. Covers all 8 supported frameworks (pytest-bdd, behave, @cucumber/cucumber, godog, cucumber-jvm-maven, cucumber-jvm-gradle, cucumber-rs, reqnroll). Agents can no longer bypass the BDD verification chain by writing plain tests.
  • check_bdd_dependency() utility: New function in common.sh that checks language-specific dependency files (requirements.txt, package.json, go.mod, pom.xml, build.gradle, Cargo.toml, *.csproj) for the expected BDD framework.

v2.1.0 – v2.1.6

  • PREMISE.md mandatory: Init now requires PREMISE.md; constitution skill validates it via script.
  • Dashboard fixes: Remove auto-reload in favor of manual refresh button; fix testify view crash, cross-link rendering, checklist/testify/analyze completion status, and active tab persistence.
  • Framework dedup: Single detect_framework() in common.sh replaces duplicated detection logic across scripts.
  • Generator single source of truth: Delete bundled generator; consistent src/ path; clearer template error messages.
  • SC-XXX traceability: Fix prose range detection for success criteria references.
  • Windows parity: Fix 19 Pester test failures, setup-windows-links parameter handling, output stream capture.
  • CI hardening: Move E2E tests from nightly to every push; Windows runner; skill review gate at 90% threshold.

v2.0.0

BREAKING — Testify generates Gherkin .feature files (replaces test-specs.md).

  • Full BDD verification chain: Hash integrity for .feature files, step coverage via dry-run (verify-steps.sh), step quality via AST analysis (verify-step-quality.sh), and framework scaffolding (setup-bdd.sh).
  • Static dashboard: Replaces the server-based process with a static HTML dashboard generated by generate-dashboard.js.
  • Analyze skill .feature traceability: Tags in .feature files are traced back to spec requirements.
  • Implement skill red-green-verify cycle: Enforces BDD chain during implementation.
  • Pre-commit hook .feature support: Assertion integrity checks extended to .feature file directories with combined hashing.
  • Gherkin template reference: Extracted to a reference file for lint compatibility.

v1.10.0

  • PREMISE.md: New app-wide context document (what/who/why/domain/scope). Drafted from PRD during init, confirmed by constitution skill. All skills load it automatically.
  • No clarify question limit: Removed the artificial 5-question cap. Clarification continues until all critical ambiguities are resolved.
  • PRD feature ordering: Features extracted from PRD are ordered in logical implementation sequence with rationale. User confirms order before issue creation.
  • Agent-aware model suggestions: Skills suggest the optimal model for the next phase, with agent-specific switch commands and a 2-week auto-refreshing cache.
  • Auto-close bugfix issues: Bugfix commits include Fixes #N for automatic GitHub issue closure on push.
  • Feature branch merge offer: Implement and taskstoissues skills offer to merge the feature branch (local merge, PR, or skip).
  • Feature-scoped issue titles: Tasks-to-issues uses [FeatureID/TaskID] format to prevent cross-feature naming conflicts.
  • Parallel issue creation: Tasks-to-issues dispatches issue creation via subagents for faster execution.
  • No gh CLI hard dependency: All GitHub operations fall back to curl with the GitHub API when gh is unavailable.

v1.9.0

  • Git/GitHub setup in init: /iikit-core init now detects the git environment (repo, remotes, gh CLI) and offers git init, gh repo create, or clone before bootstrapping IIKit.
  • PRD seeding: /iikit-core init [doc] reads an existing PRD/SDD document, extracts features, and creates labeled GitHub issues as a backlog.
  • Auto-commit per task: /iikit-07-implement commits after each completed task with Conventional Commits format (feat(<feature-id>): <task-id> <desc>) and iikit-feature/iikit-task trailers for spec-to-commit traceability.

v1.6.0

  • Bugfix skill: New /iikit-bugfix utility skill for reporting and fixing bugs without the full specify/clarify/plan/checklist workflow. Creates structured bugs.md records, generates fix tasks, and integrates with GitHub Issues (inbound import and outbound creation). Cross-platform scripts (bash + PowerShell).
  • Multi-feature support: Sticky feature selection via .specify/active-feature file that survives session restarts. Detection cascade: active-feature file > SPECIFY_FEATURE env > git branch > single feature auto-select.
  • SessionStart hooks: Hooks for Gemini CLI and OpenCode that set terminal title and load context on session start.
  • Tessl eval integration: /iikit-02-plan now queries Tessl evals for tech selection and dashboard metrics.
  • Bug detection in specify: /iikit-01-specify now detects bug-fix-like descriptions and suggests redirecting to /iikit-bugfix.
  • Post-fix GitHub comments: /iikit-07-implement comments on linked GitHub issues after completing bug fix tasks.
  • Improved skill definitions: Conciseness improvements and progressive disclosure across all skills.
  • Unified docs: Tile index.md symlinked to README.md for single source of truth.

v1.5.0

  • Spec item references in clarifications: Clarification Q&A entries now include spec item references (FR-xxx, US-x, SC-xxx) for full traceability from clarifications back to the spec items they affect.

v1.4.1

  • Publish action migration: Migrated to official tesslio/publish GitHub Action.

v1.4.0

  • Per-feature context: context.json now lives inside each feature's spec directory, enabling better isolation between features.
  • Analyze file output: The analyze skill writes its results to a file for dashboard consumption.
  • ASCII box borders: Fixed misaligned borders in plan and core skill output.

v1.3.0

  • Parallel subagent execution: The implement skill now runs independent tasks in parallel via subagents for faster execution.
  • Single source of truth: Skills are authored once in .claude/skills/ with symlinks for other agents.

v1.2.0

  • Live kanban dashboard: The implement skill (/iikit-07-implement) now automatically launches a browser-based kanban board via npx iikit-kanban. Watch user stories move through Todo / In Progress / Done columns as the AI agent checks off tasks in real time. Dark/light theme, collapsible task lists, integrity badges. Gracefully skips if Node.js is not available.

v1.1.0

  • Git hooks for assertion integrity: Pre-commit hook blocks tampered assertions. Post-commit hook stores hashes as tamper-resistant git notes. Defense-in-depth with dual-layer verification — works agent-agnostically because git triggers the hooks, not the agent.

v1.0.x

  • Initial release with 10-phase specification-driven workflow, assertion integrity hashing, constitution enforcement, TDD support, and cross-platform (Bash + PowerShell) scripts.