pm-spec

Generate structured markdown feature specs from product ideas.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/basilebong/basile-cc-marketplace --skill pm-spec-basilebong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/basilebong/basile-cc-marketplace/tree/main/plugins/pm-spec/skills/pm-spec
Command: npx skills add https://github.com/basilebong/basile-cc-marketplace --skill pm-spec-basilebong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a dedicated product manager to explore codebases, gather precise requirements, and produce clear feature specifications, leading to ambiguous designs and delayed development.

Core Features & Use Cases

  • Conducts thorough codebase exploration to identify relevant components and dependencies.
  • Asks targeted questions to resolve every requirement ambiguity, ensuring a complete spec.
  • Runs an automated reviewer panel (UX, Security, Architecture, Business) to validate and refine the draft before saving.

Quick Start

Ask Claude to act as a product manager and generate a feature spec for your idea.

Frequently Asked Questions about pm-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a feature spec from product ideas without a dedicated product manager?

To generate a feature spec, an AI product manager explores your codebase, asks targeted questions to resolve ambiguities, and runs a reviewer panel to validate the draft before saving a structured markdown specification.

What is the best way to write user stories that fit my existing software architecture?

Writing user stories that fit your architecture requires thorough codebase exploration to identify relevant components and dependencies, followed by iterative requirement gathering to ensure the resulting feature spec aligns with your system.

How does an automated reviewer panel refine feature specifications?

An automated reviewer panel refines feature specifications by evaluating drafts across UX, Security, Architecture, and Business domains, validating and updating the document before saving the final markdown spec.

Do I need a specific environment to draft and save feature specifications?

Drafting feature specifications requires a development environment where the tool can explore your codebase and save the final structured markdown output directly into a local .claude/specs directory.

Can I use this approach for complex software development projects requiring code exploration?

Yes, this approach suits software development projects that require extensive codebase exploration, iterative questioning to clarify requirements, and structured spec drafting to align design with development goals.

Why does requirement gathering involve iterative questioning during spec drafting?

Requirement gathering involves iterative questioning to resolve every ambiguity in product ideas, ensuring the generated feature specification contains precise requirements before the reviewer panel validation loop begins.