Skip to content

v2.3.0 — /release + /setup integration for agent-toolkit's /design skill

Choose a tag to compare

View all tags
@alexherrero alexherrero released this 15 May 18:09
· 380 commits to main since this release
v2.3.0
18e1335

Additive minor — no breaking changes. Two harness extensions that integrate with the new agent-toolkit v0.8.0 /design skill: a /release lifecycle hook that auto-promotes queued plans + transitions design Status final → launched + surfaces launched designs in the wiki; and a /setup scaffolding extension for the wiki/explanation/designs/ landing dir. Plus a /work Step 11 summary template enhancement that applies to any harness install with a ROADMAP-driven multi-plan project.

Integration points

agent-toolkit v0.8.0 ships the /design skill with three sub-commands. The skill's third sub-command (/design sequence) writes a first PLAN.md to <project>/.harness/PLAN.md + queues subsequent parts at <project>/.harness/designs/<doc-slug>/queued-plans/<part-slug>.PLAN.md. v2.3.0's harness extensions consume that queue:

  • /release §1b auto-promotes the next queued plan when the active completes (Case B), or transitions the parent design final → launched + surfaces it in wiki/Home.md + _Sidebar.md when the last part ships (Case C).
  • /setup §7 scaffolds the wiki/explanation/designs/ landing dir so target projects have the destination ready before the first design.

Without agent-toolkit installed alongside, both extensions silent-skip — the harness works standalone exactly as v2.2.0.

§1b three cases at a glance

Case Detection Action
A — not design-sourced No parent_design_doc: frontmatter + no queued-plans/ dir Silent no-op; existing /release flow continues
B — more queued plans exist Design-sourced + at least 1 file remaining in queued-plans/ Archive completed plan; promote next queued plan via mv; append parent Document History; halt /release with operator-facing next-step message
C — LAST queued plan Design-sourced + this was the last file in queued-plans/ Archive; transition parent design Status final → launched; append Document History; if visibility: published update wiki/Home.md + _Sidebar.md to surface in a Designs section (idempotent); continue with §2-§9 — this IS a real release

Universal /work Step 11 enhancement

Separately from the design-skill integration, /work Step 11 (the close-out summary) gains an opt-in richer template for ROADMAP-driven multi-plan projects (signal: .harness/ROADMAP.md present). Single-plan installs keep the existing minimal ≤5-bullet summary; multi-plan projects get:

  • Roadmap context lead-in
  • Plan-status chart with ✅/⬜ symbols per task
  • Link block to .harness/ROADMAP.md / PLAN.md / progress.md
  • Explicit handoff phrase
  • Optional commit SHA / CI status with per-OS times / key design calls / scope adjustments

Universal applicability — any harness install with a roadmap benefits. Came out of the dev-flow codification work (commit ce86977); shipping in this release window alongside the design-skill integration.

Migration

No migration needed — purely additive. To enable the new sections' design-skill dispatch in your projects, install agent-toolkit v0.8.0 alongside the harness:

# If you don't already have agent-toolkit cloned as a sibling:
gh repo clone alexherrero/agent-toolkit ../agent-toolkit

# Install into your project (lands the /design skill at .claude/skills/, etc.):
bash ../agent-toolkit/install.sh /path/to/your-project

Without the toolkit, /release and /setup continue to satisfy the phase contracts using the existing flows.

Decision rationale

The design decision (hybrid decomposition; user's 10-section template; canonical wiki entry point; one-PLAN.md-per-part; skill-ships-in-toolkit-not-harness; tool allowlist; mid-execution audit-trail via Document History) lives in agent-toolkit ADR 0004 since the customization itself lives there.

See CHANGELOG.md for the full v2.3.0 entry.

Assets 2
Loading