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 |
evaluations/spec-to-tasks.json
View on GitHub{
"name": "Create Tasks from Specification",
"skills": ["spec-to-implementation", "task-manager"],
"query": "Read the Payment Integration spec and create implementation tasks in our Tasks database",
"expected_behavior": [
"Step 1: Uses Notion:notion-search to find Payment Integration spec or asks for URL",
"Step 2: Fetches spec page using Notion:notion-fetch to read full content",
"Step 3: Parses spec using reference/spec-parsing.md patterns to identify work items",
"Step 4: Breaks down into appropriately-sized tasks using breakdown patterns from reference/task-creation.md",
"Step 5: Uses Notion:notion-search to find Tasks database location",
"Step 6: Fetches Tasks database using Notion:notion-fetch to get schema, property names, and data sources",
"Step 7: Identifies correct data source from <data-source> tags in fetch results",
"Step 8: Optionally creates implementation plan page first (recommended per workflow)",
"Step 9: For each task - creates task page using Notion:notion-create-pages with parent: { data_source_id: 'collection://...' }",
"Step 10: Sets task properties from schema: Title, Status (To Do), Priority, Related Tasks (link to spec)",
"Step 11: Includes task description with context, acceptance criteria from spec, dependencies",
"Step 12: Links tasks to spec page using <mention-page> and to each other for dependencies",
"Step 13: Sequences tasks appropriately (setup → implementation → testing per reference/task-creation.md)",
"Step 14: Reports summary: 'Created X tasks for Payment Integration: [task list with links]'"
],
"success_criteria": [
"Spec is found using Notion:notion-search before attempting to fetch",
"Task database is found using Notion:notion-search before attempting to fetch schema",
"Database schema is fetched and data source identified from <data-source> tags",
"Multiple tasks created (at least 3-5) covering spec scope",
"Tasks are right-sized per reference/task-creation.md (1-2 days each)",
"Each task has clear acceptance criteria extracted from spec",
"Tasks are properly sequenced with dependencies using relation properties",
"All tasks link back to original spec using mention-page tags",
"Task properties match exact schema from fetched database",
"Tasks use correct parent (data_source_id: 'collection://...') for database placement",
"Uses correct tool names and sequence: Notion:notion-search (2x) → Notion:notion-fetch (2x) → Notion:notion-create-pages (Nx)"
]
}
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 |