Agent Specification
技能 已验证 活跃Agent skill for specification - invoke with $agent-specification
To assist users in creating detailed and structured software specifications, ensuring clarity, testability, and alignment with project goals.
功能
- Guides through SPARC specification phase
- Facilitates requirements gathering
- Analyzes technical, business, and regulatory constraints
- Defines use cases with preconditions and exceptions
- Generates acceptance criteria in Gherkin format
使用场景
- Defining functional and non-functional requirements for new software.
- Documenting constraints (technical, business, regulatory) for a project.
- Creating detailed use cases and scenarios.
- Establishing clear acceptance criteria for project deliverables.
非目标
- Implementing or coding the software itself.
- Managing project execution beyond the specification phase.
- Providing legal or regulatory advice.
工作流
- Initiate specification process
- Gather functional and non-functional requirements
- Analyze technical, business, and regulatory constraints
- Define use cases, preconditions, flows, and exceptions
- Document acceptance criteria
- Complete the specification phase
实践
- Requirements Analysis
- Specification Design
- Quality Assurance Planning
先决条件
- Access to Claude Code environment
安装
npx skills add ruvnet/ruflo通过 npx 运行 Vercel skills CLI(skills.sh)— 需要本地安装 Node.js,以及至少一个兼容 skills 的智能体(Claude Code、Cursor、Codex 等)。前提是仓库遵循 agentskills.io 格式。
质量评分
已验证类似扩展
Presentation Structure
100关于演示文稿幻灯片格式、权重系统、导航和章节结构的知识
Analyze Codebase For Mcp
99Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do versus what is already exposed via MCP, or generating a tool spec to hand off to scaffold-mcp-server.
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.
Performance Analysis
100Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms