Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnotion-spec-to-implementationExecute the skills CLI command in your project's root directory to begin installation:
Fetches notion-spec-to-implementation from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate notion-spec-to-implementation. Access via /notion-spec-to-implementation in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Notion:notion-search, then fetch it with Notion:notion-fetch.reference/spec-parsing.md.Notion:notion-create-pages (pick a template: quick vs. full).Notion:notion-create-pages.Notion:notion-update-page.codex mcp add notion --url https://mcp.notion.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login notionAfter successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
Notion:notion-search); if multiple hits, ask the user which to use.Notion:notion-fetch) and scan for requirements, acceptance criteria, constraints, and priorities. See reference/spec-parsing.md for extraction patterns.reference/quick-implementation-plan.md.reference/standard-implementation-plan.md.Notion:notion-create-pages, include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria. Link back to the spec.Notion:notion-search → Notion:notion-fetch to confirm the data source and required properties). Patterns in reference/task-creation.md.reference/task-creation-template.md for content (context, objective, acceptance criteria, dependencies, resources).Notion:notion-create-pages using the database's data_source_id.Notion:notion-update-page.reference/progress-tracking.md.reference/progress-update-template.md; close phases with reference/milestone-summary-template.md.reference/ — parsing patterns, plan/task templates, progress cadence (e.g., spec-parsing.md, standard-implementation-plan.md, task-creation.md, progress-tracking.md).examples/ — end-to-end walkthroughs (e.g., ui-component.md, api-feature.md, database-migration.md).Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: notion-spec-to-implementation is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend notion-spec-to-implementation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in notion-spec-to-implementation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
notion-spec-to-implementation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
notion-spec-to-implementation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in notion-spec-to-implementation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for notion-spec-to-implementation matched our evaluation — installs cleanly and behaves as described in the markdown.
notion-spec-to-implementation has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: notion-spec-to-implementation is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for notion-spec-to-implementation matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 66