Write Spec
技能 活跃Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
To efficiently transform vague ideas or user requests into structured, actionable product specifications and PRDs, ensuring clarity and scope definition.
功能
- Generates feature specs and PRDs
- Supports various input types (feature name, problem statement, idea)
- Gathers context through conversational prompts
- Integrates with connected tools (project tracker, knowledge base, design)
- Outputs structured documents with defined sections (Goals, Non-Goals, User Stories, Requirements)
使用场景
- Turning a vague idea into a structured document
- Scoping a feature with clear goals and non-goals
- Defining success metrics and acceptance criteria
- Breaking a large feature request into phased specifications
非目标
- Implementing the feature described in the spec
- Designing the user interface or user experience
- Making technical implementation decisions
- Managing the project timeline or dependencies beyond documenting them
Trust
- warning:Issues AttentionIn the last 90 days, 29 issues were opened and 4 were closed, indicating a low closure rate and potentially slow maintainer response to open issues.
安装
请先添加 Marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install product-management@knowledge-work-plugins质量评分
类似扩展
Measure Dashboard Requirements
100Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams, defining KPI tracking, or documenting reporting needs.
Acceptance Criteria Generator
99Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
Pm Prd
98Generate a Product Requirements Document (PRD) with four modes: Full PRD for net-new features, Lightweight Feature Spec for sprint-level work, Iteration/V2 Spec for follow-ups on shipped features, and Migration/Compliance Spec for regulatory or API migrations. Enforces problem-first thinking, leading + lagging metrics, non-goals, and testable acceptance criteria. Use when someone says "PRD", "product requirements", "feature spec", "write a spec", "requirements document", "what to build", "engineering spec", "technical requirements", "migration spec", "compliance spec", "V2 spec", or "iteration spec".
Feature Forge
98Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.
Agent Specification
95Agent skill for specification - invoke with $agent-specification
Teach Guidance
100Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.