A few months ago I shipped the first version of a feature-workflow plugin for Claude Code. The model is file-driven: idea.md means it's in the backlog, idea.md + plan.md means it's in progress, idea.md + plan.md + shipped.md means it's done. A post-write hook regenerates a DASHBOARD.md from the directory tree. External reviewers (Gemini or Codex) gate the plan and the implementation via GitHub Actions.
That much works. The shape of how I use the plugin has shifted since then, and the schema and tooling have grown to match. The additions worth a follow-up post: state that's orthogonal to the file-presence lifecycle, search across the backlog without grep, three modes of per-feature review, an autopilot loop that drives a single feature from plan to ship without manual prompting, an epic dispatch path that walks a parent feature's children sequentially or in parallel waves with worktree-isolated subagents, and a reviewer-side check that catches drive-by static-analysis suppressions before they merge.
This post walks through what each of those does and how they fit together.