From productize-all
PRDs from industry and feature specifications. Use when the user needs a product workflow for business analysis related to prds from industry and feature specifications. Trigger terms: pm, prd, requirements, documentation, business-analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/productize-all:prds-from-industry-and-feature-specificationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->
Before producing the artifact, implementation step, or code change, classify the work:
Operating rules:
AskUserQuestion: <one question> Why it matters: <decision it changes>.completed, blocked, deferred, or needs-review when runtime hooks are available.Artifact format policy:
$implementation-notes when the user asks for a running notes file, especially implementation-notes.html or implementation-notes.md.Runtime hooks, if available:
productize-workflow start "<user request>" at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.productize-workflow complete --id <id> --status completed|blocked|deferred|needs-review --artifact-type <type> --summary <summary> before ending durable product work; it records the artifact, saves context, and logs completion status.productize-update-check --strict at the start of maintenance, setup, release, or generated-output work.productize-config to read or write user/team preferences such as persona, artifact mode, evidence threshold, or update-check policy.productize-session-log to record important workflow decisions.productize-artifact-log when a durable artifact is produced.productize-context-restore before restarting long-running product work from scratch.productize-context-save after producing a durable strategy, research, spec, or stakeholder artifact.productize-registry-search or productize-skill-router when routing is ambiguous.productize-completion-status to log whether the workflow completed, blocked, deferred, or needs review.Telemetry standard:
.productize/ or PRODUCTIZE_STATE_DIR.Current skill metadata:
prds-from-industry-and-feature-specificationsUse this skill to run the Productize prompt contract for PRDs from industry and feature specifications.
{{PLACEHOLDER}} in the contract as an input to collect, infer, or mark as missing.GOAL, CONSTRAINTS, FORMAT, and FAILURE clauses exactly.INPUTS <provided_inputs>
GOAL
Create a complete, implementation-ready PRD for FEATURE_NAME in the specified INDUSTRY and DEVELOPMENT_STAGE.
Success metric:
CONSTRAINTS
CURRENT_KNOWLEDGE and CURRENT_SOLUTION; do not contradict provided context without explicit rationale.FORMAT.FORMAT Return exactly this structure:
# [Product Name][High-level overview of the product and goal.]
[Market context, competitors, trends, and target users.]
[Core user problem, pain points, and why existing solutions are insufficient.]
[Proposed AI product solution and how it addresses the problem.]
| Feature | Reach | Impact | Confidence | Effort | RICE Score | Priority |
|---|---|---|---|---|---|---|
Functional Requirements:
AI/ML Model Requirements:
Non-Functional Requirements:
[Key product, technical, data, and go-to-market challenges.]
| Use Case | Target User | Key Benefit | Differentiator |
|---|---|---|---|
[Success metrics and north star metric.]
Stakeholders & Communication
Roll-out Strategy
FAILURE
FORMAT is missing or materially incomplete.npx claudepluginhub itseffi/productize --plugin productize-allCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.