productizer
v4.37.1Requirements tracking for Claude Code. One living spec per product: every intent is classified against everything already agreed, a contradiction stops the work instead of merging, and each release regenerates its own guide and announcement.
By Itay GlickLicense: MIT0 GitHub starsUpdated 3 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Sep 3, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install productizer for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install productizer@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/gitayg/productizerClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/productizer/.
Plugin files
├── .claude-plugin/plugin.json├── skills/answer/SKILL.md├── skills/backlog/SKILL.md├── skills/check/SKILL.md├── skills/dashboard/SKILL.md├── skills/help/SKILL.md└── skills/import/SKILL.md
Included Skills6
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.
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.
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.
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.
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.
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.
Plugin manifests1
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "productizer",
"displayName": "Productizer",
"version": "4.37.1",
"description": "Requirements tracking for Claude Code. One living spec per product: every intent is classified against everything already agreed, a contradiction stops the work instead of merging, and each release regenerates its own guide and announcement.",
"author": {
"name": "Itay Glick"
},
"repository": "https://github.com/gitayg/productizer",
"license": "MIT",
"keywords": [
"requirements",
"living-spec",
"spec-driven",
"sdlc",
"governance",
"ears",
"evals",
"review"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[productizer on Agent Plugins Marketplace](https://pluginsmp.com/plugins/productizer)