productizer
ListedRequirements tracking for Claude Code. One living spec per product: every intent is classified against everything already agreed, and a contradiction stops the work instead of merging.
Bundles
Everything this plugin ships — skills, agents, commands, hooks, and MCP servers it bundles.
Skills (7)
answer
Find every question this repo is holding open for a person and put them one at a time — contradictions waiting on a ruling, requirements nothing asserts, blocked items, checks that refused. Records each answer in the files. Use when asked what needs a decision, what is waiting on me, what questions are open, or to work through the open questions.
backlog
Show the backlog — the queue in front of the lifecycle — and add to it, reorder it, or start work on an item. Everything here is a want, not a requirement: nothing in the backlog has been agreed. Use when asked what is queued, what is next, to add something to the backlog, to reprioritise, or to pick up an item.
check
Run this repo's declared checks — Stage 5 — over the current change, and report what passed, what failed, and what could not be measured. Use when asked to run the checks, run the gate, see if this change passes, or check before committing or releasing.
dashboard
Regenerate the Productizer dashboard from this repo's own files and publish it as a page. Shows the living spec, the backlog queue, the board of what is actually in flight, the last check run, releases, and what each declared check cannot see. Use when asked to see the dashboard, the pipeline, the spec at a glance, what is in flight, what is waiting on a person, or the state of the lifecycle.
help
List every Productizer command with what it does and when to reach for it, read from the installed plugin rather than from memory. Use when asked what productizer can do, what the commands are, how to use it, where to start, or which command to use for something.
import
Onboard a repository that already exists — Stage 0c. Surveys the code read-only for what it can actually evidence, then drafts requirements from that evidence, every one marked inferred and unconfirmed until a person confirms it. If the repo already holds a spec, the same evidence is drift rather than a draft, and it asks what to do instead of guessing. Use when adopting the lifecycle in an existing project, bringing a legacy repo under a spec, importing a codebase, checking a repo against its own spec, or asking what this repo already does.
spec
Run the AI-native software lifecycle. An intent arrives as a GitHub Issue, a Jira ticket, typed text or a file; it is classified against the repo's living spec at .claude/productizer/spec.md (extend, refine, duplicate, or contradict), merged as a spec delta, then planned and built. Use whenever the user starts a new feature, idea, bug or change and wants it done properly end-to-end; asks to capture an intent, update the spec, write an implementation plan, CLAUDE.md, review policy, approval gate, eval suite or control bands; asks whether something is already specified or contradicts existing requirements; asks how to adopt Claude across an SDLC or make agentic development governable and auditable; or asks what stage a piece of work is in and what comes next; or asks to SEE the pipeline, the spec, the fleet across repos, or a control band, which is published as a read-only view. Also use when wiring the lifecycle to GitHub Issues or Jira — picking a source of truth, binding a repo or project key, or moving tick
Hooks (1)
Quality Score: 49/100
Details
- Author
- gitayg
- Repository
- gitayg/productizer
- Created
- 2 weeks ago
- Last Updated
- 2 days ago
- Language
- Shell
- License
- MIT