shape-spec
Research and gather requirements for a new feature spec. Use when you have a feature idea and need to understand scope, gather requirements, and document visuals before writing a spec.
When & Why to Use This Skill
The shape-spec skill is designed to bridge the gap between initial feature ideation and technical implementation. It automates the 'shaping' process by conducting deep research, analyzing existing codebase patterns, and gathering comprehensive requirements. By utilizing tools like oracle for feasibility and finder for code analysis, it ensures that developers and product managers have a well-defined scope, documented visuals, and clear acceptance criteria before a single line of production code is written.
Use Cases
- Feature Scoping: Transform a high-level feature idea into a structured roadmap item by analyzing user goals and technical constraints.
- Technical Feasibility Analysis: Use AI-driven research to evaluate the complexity of a new requirement against the existing codebase architecture.
- Standardized Requirement Documentation: Automatically initialize a dedicated planning directory with requirements.md and visual assets to ensure team-wide alignment.
- Codebase Pattern Discovery: Identify reusable components and existing implementation patterns to ensure the new feature remains consistent with the current system design.
| name | shape-spec |
|---|---|
| description | Research and gather requirements for a new feature spec. Use when you have a feature idea and need to understand scope, gather requirements, and document visuals before writing a spec. |
Shape Spec
Research and define requirements before writing a detailed specification.
When to Use
- You have a feature idea to explore
- Need to gather requirements before implementation
- Want to scope out a roadmap item
Workflow
Initialize Spec Directory
amp-os/specs/[feature-name]/ ├── planning/ │ ├── requirements.md │ └── visuals/Research with Oracle
- Call
oracle: "Help me research and scope this feature: [description]" - Include: user goals, constraints, existing patterns
- Call
Codebase Analysis
- Use
finderto find related existing code - Identify reusable patterns and components
- Load
amp-os-code-analysisskill for structured analysis
- Use
Gather Requirements
- Document user stories
- Define acceptance criteria
- Note technical constraints
- Save to
planning/requirements.mdusing requirements-template.md
Collect Visuals
- Add mockups/screenshots to
planning/visuals/
- Add mockups/screenshots to
Resources
Amp Tools to Use
oracle- Scope analysis and feasibilityfinder- Find related code patternsRead- Analyze existing implementations