pm-spec-writing
Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
Profile →npx skills add rampstackco/claude-skills --skill pm-spec-writing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PM Spec Writing Take an idea (often vague) and turn it into a specification a developer or AI agent can actually build from. Stack-agnostic. Works for new features, bug fixes, content changes, or infrastructure work. --- ## When to use - Translating an idea into a buildable feature spec - Writing a PRD or product requirement document - Filing a bug report that someone else can act on - Scoping a project before kickoff - Prioritizing a backlog of feature requests - Writing acceptance criteria for an existing feature - Breaking a large initiative into shippable increments ## When NOT to use - Quarterly or annual planning across multiple initiatives (use `roadmap-planning`) - Code review or debugging existing code (use `code-review-web`) - Design decisions for a feature already specced (use `design-standards`) - User research to validate an idea (use `ux-research`) --- ## Required inputs - The idea, request, or problem being addressed - The audience or user affected - Any existing constraints (stack, deadlines, dependencies) - The success metric (how will you know it worked?) If the idea is vague, the workflow's first step is clarification. Do not write specs around vagueness. --- #
- When to use
- When NOT to use
- Required inputs
- The framework: 4 phases
- Phase 1: Clarify the idea
- Phase 2: Scope by impact and effort
- Phase 3: Write the spec
- Phase 4: Sequence and ship
- Workflow
- Failure patterns
- Output format
- Reference files
What does the pm-spec-writing skill do?
Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill pm-spec-writing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.