productizer

Plugin productizer from marketplace productizer in gitayg/productizer. Commands read from the repo's manifest — 9 days ago.

Skills (8)

• 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

• 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 pic

• 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 s

• 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 th

• spec-review

  Review the whole living spec and constitution against each other — the read intake never makes, because intake checks one intent at a time. Part A runs the deterministic spec checks verbatim; Part B is an advisory, fresh-context review for what no script decides: semantic contradictions, paraphrased

• 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

Slash commands (1)

• /productizer:upgrade

  Report what this repo installed from an older version of this plugin and has never been told about: hooks that drifted from their templates, schema versions left behind, checks the plugin now ships that this repo never declared, and content the templates gained. Reports only. Applies nothing.

Similar plugins