Prat011/awesome-llm-skills / notion-spec-to-implementation
notion-spec-to-implementation
UnverifiedTurns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.
| File | Kind | Size |
|---|---|---|
| .DS_Store | binary | 6.0 KB |
| SKILL.md | skill md | 8.5 KB |
| evaluations/.DS_Store | binary | 6.0 KB |
| evaluations/README.md | markdown | 4.3 KB |
| evaluations/basic-spec-implementation.json | config | 2.3 KB |
| evaluations/spec-to-tasks.json | config | 2.5 KB |
| examples/api-feature.md | markdown | 13.3 KB |
| examples/database-migration.md | markdown | 2.4 KB |
| examples/ui-component.md | markdown | 1.6 KB |
| reference/milestone-summary-template.md | markdown | 456 B |
| reference/progress-tracking.md | markdown | 8.8 KB |
| reference/progress-update-template.md | markdown | 420 B |
| reference/quick-implementation-plan.md | markdown | 480 B |
| reference/spec-parsing.md | markdown | 6.8 KB |
| reference/standard-implementation-plan.md | markdown | 3.2 KB |
| reference/task-creation-template.md | markdown | 597 B |
| reference/task-creation.md | markdown | 7.8 KB |
reference/standard-implementation-plan.md
View on GitHub# Standard Implementation Plan Template
Use this template for most feature implementations.
```markdown
# Implementation Plan: [Feature Name]
## Overview
[1-2 sentence feature description and business value]
## Linked Specification
<mention-page url="...">Original Specification</mention-page>
## Requirements Summary
### Functional Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
### Non-Functional Requirements
- **Performance**: [Targets]
- **Security**: [Requirements]
- **Scalability**: [Needs]
### Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
## Technical Approach
### Architecture
[High-level architectural decisions]
### Technology Stack
- Backend: [Technologies]
- Frontend: [Technologies]
- Infrastructure: [Technologies]
### Key Design Decisions
1. **[Decision]**: [Rationale]
2. **[Decision]**: [Rationale]
## Implementation Phases
### Phase 1: Foundation (Week 1)
**Goal**: Set up core infrastructure
**Tasks**:
- [ ] <mention-page url="...">Database schema design</mention-page>
- [ ] <mention-page url="...">API scaffolding</mention-page>
- [ ] <mention-page url="...">Authentication setup</mention-page>
**Deliverables**: Working API skeleton
**Estimated effort**: 3 days
### Phase 2: Core Features (Week 2-3)
**Goal**: Implement main functionality
**Tasks**:
- [ ] <mention-page url="...">Feature A implementation</mention-page>
- [ ] <mention-page url="...">Feature B implementation</mention-page>
**Deliverables**: Core features working
**Estimated effort**: 1 week
### Phase 3: Integration & Polish (Week 4)
**Goal**: Complete integration and refinement
**Tasks**:
- [ ] <mention-page url="...">Frontend integration</mention-page>
- [ ] <mention-page url="...">Testing & QA</mention-page>
**Deliverables**: Production-ready feature
**Estimated effort**: 1 week
## Dependencies
### External Dependencies
- [Dependency 1]: [Status]
- [Dependency 2]: [Status]
### Internal Dependencies
- [Team/component dependency]
### Blockers
- [Known blocker] or None currently
## Risks & Mitigation
### Risk 1: [Description]
- **Probability**: High/Medium/Low
- **Impact**: High/Medium/Low
- **Mitigation**: [Strategy]
### Risk 2: [Description]
- **Probability**: High/Medium/Low
- **Impact**: High/Medium/Low
- **Mitigation**: [Strategy]
## Timeline
| Milestone | Target Date | Status |
|-----------|-------------|--------|
| Phase 1 Complete | [Date] | ⏳ Planned |
| Phase 2 Complete | [Date] | ⏳ Planned |
| Phase 3 Complete | [Date] | ⏳ Planned |
| Launch | [Date] | ⏳ Planned |
## Success Criteria
### Technical Success
- [ ] All acceptance criteria met
- [ ] Performance targets achieved
- [ ] Security requirements satisfied
- [ ] Test coverage > 80%
### Business Success
- [ ] [Business metric 1]
- [ ] [Business metric 2]
## Resources
### Documentation
- <mention-page url="...">Design Doc</mention-page>
- <mention-page url="...">API Spec</mention-page>
### Related Work
- <mention-page url="...">Related Feature</mention-page>
## Progress Tracking
[This section updated regularly]
### Phase Status
- Phase 1: ⏳ Not Started
- Phase 2: ⏳ Not Started
- Phase 3: ⏳ Not Started
**Overall Progress**: 0% complete
### Latest Update: [Date]
[Brief status update]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |