Skip to content

v0.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Jun 01:09
· 39 commits to main since this release
v0.2.0
27168c9

v0.2.0

[0.2.0] — 2026-05-27

The "7-agent factory" + repo-discipline release. Splits the per-task cadence into 6 steps (acceptance verifier + read-only validator added), introduces folder-scoped backend / frontend builders for cross-layer phases, ships the /ship vertical-slice orchestrator command, hardens HTML companions with anti-AI-slop quality floor + style presets, and bakes the full CHANGELOG / PR-label / Conventional-Commits discipline into the skill so every project (including this repo) follows it.

Added

  • references/user-story.md — mandatory user-story + numbered acceptance criteria file for any user-observable phase. Signed off BEFORE spec is written; becomes the ground truth for the new acceptance verifier (cadence step 1.5) and the validator (cadence step 2). AC IDs are stable and appear in test names.
  • references/builder-split.md — backend-builder + frontend-builder folder-scoped split for cross-layer phases. Defines the CLAUDE.md folder-map schema, per-builder prompt templates, and the Builder Summary handoff contract (Cross-layer contract section that frontend consumes verbatim, never silently massaging bad shapes).
  • Cadence step 1.5 — acceptance verifier: independent subagent, read-only on src/, writes exactly one acceptance test per AC and reports per-AC PASS/FAIL/UNTESTABLE. Acceptance tests live in tests/acceptance/ separately from builder unit/integration tests.
  • Cadence step 2 — Validator (replaces former "spec compliance review"): independent read-only subagent that compares the diff against user-story.md + spec + Builder Summaries + Acceptance Verifier Report. Never edits, never invents findings, never does code-quality (step 3 owns that). Lens: correctness-vs-promise + scope drift + folder boundary + security gaps vs spec.
  • commands/ship.md (new /ship slash command) — vertical-slice orchestrator chaining researcher → story → spec → BE → FE → acceptance verifier → validator → fix loop → PR. 3 human checkpoints (story / spec / PR); everything else runs unattended. Designed for one user-observable feature inside an active phase.
  • references/html-companion-template.md — new "Optional frontmatter" section (node / audience / design_system / generated / source) so multi-node projects can tag artifacts and match presets. Pattern adapted from nexu-io/html-anything.
  • references/html-companion-template.md — new "Style preset recommendations" section mapping each opt-in node to a preset (default-cool / kami-parchment / swiss-grid / xhs-pastel). Presets swap palette + font + radius only; section list and badge taxonomy stay the contract.
  • references/html-companion-template.md — new "Quality floor (anti-AI-slop hard rules)" section with 4 enforced constraints: CJK-first font stack on CJK projects, 8 px baseline grid, WCAG AA contrast (≥4.5 body / ≥3.0 ≥18 px), must-use-real-data rule. Adapted from alchaincyf/huashu-md-html discipline.
  • scripts/commands-manifest.txt + commands/ directory in repo — curated allow-list governing which user-local slash commands ship with the plugin (NOT the whole ~/.claude/commands/ dir).
  • scripts/sync.sh — extended to push/pull/check both skill (whole-dir rsync) and commands (per-file mirror via manifest); validator reconciles manifest ↔ disk (no orphans either way).
  • scripts/validate.py — extended to check command frontmatter + manifest reconciliation.
  • CHANGELOG.md (this file) + .github/release.yml (PR-label-driven auto release notes) + CONTRIBUTING.md (commit / changelog / PR-label discipline). references/changelog.md bakes the same discipline into the skill itself.

Changed

  • Per-task cadence bumped from 5 steps to 6: implementer(s) → acceptance verifier (NEW step 1.5) → validator (formerly "spec compliance review", now hardened) → code quality review → fixup → journal. Layer-pure mechanical tasks compress (skip step 1.5; merge step 2 + step 3) when small-diff + no-new-logic + no-security-surface.
  • Cadence step 1 — implementer dispatch now splits into 1a backend-builder + 1b frontend-builder for any cross-layer phase, per builder-split.md. Single-implementer pattern retained for layer-pure phases.
  • SKILL.md workflow step 1 (brainstorm) — adds user-story sign-off as a hard checkpoint BEFORE spec is written for any user-observable phase.
  • references/cadence.md — controller anti-patterns expanded with: cross-layer phase as single implementer (block), FE dispatched before BE summary exists (block), validator given Edit/Write (block), acceptance verifier writing against internals (block), acceptance verifier marking "covered" without a passing test (block).
  • SKILL.md — Red Flags expanded with: user-observable phase started without user-story.md, spec written before story signed off, cross-layer single implementer, FE silently massaging bad BE shape, builder edits outside folder scope, validator invents findings to look thorough, AC IDs renumbered mid-phase, all 4 html-companion quality-floor rules.
  • README.md — restructured around the 5 questions a new user asks (what is this / when to use / what's inside / setup / use). Cut from 270 to 186 lines. References grouped by purpose (per-phase / per-task cadence / delivery+CI / output discipline / meta) instead of one flat list.

Deprecated

  • "Spec compliance review" as a separate cadence step label — folded into the new Validator (cadence step 2) which is strictly broader (AC coverage + scope drift + security gaps vs spec + folder boundary, all read-only). Existing references to the old name in older phase docs remain valid but should not be created going forward.

Full history: see CHANGELOG.md

Full Changelog: https://github.com/Victoriakaey/project-life-cycle/commits/v0.2.0

Assets 2
Loading