Agent skill

Notion Spec To Implementation

by rongxinzy in rongxinzy/RongxinAI

Turns product or tech specs into concrete Notion tasks that Claude code can implement.

AGPL-3.0Auto-check passedAgent Workflows

Install Notion Spec To Implementation

skills CLI
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/MCPs/notion/skills/spec-to-implementation .claude/skills/notion-spec-to-implementation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
notion-spec-to-implementation
GitHub stars
154
Used in
2 other repos
Token cost
~2.2k tokens
SKILL.md length
648 words
Files
15
Skills in repo
94
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Turns product or tech specs into concrete Notion tasks that Claude code can implement.

  • Works in 8 steps: Find the specification → Fetch and analyze specification → Create implementation plan → …
  • Tasks that involve Planning
  • SKILL.md covers Quick Start, Implementation Workflow, Spec Analysis Patterns and Implementation Plan Structure, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Notion Spec To Implementation is an agent skill from rongxinzy/RongxinAI. Turns 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.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files (for example `evaluations/README.md`, `evaluations/basic-spec-implementation.json` and `evaluations/spec-to-tasks.json`).

It sits in Agent Workflows, covering Planning and User stories. It works with Notion. The repository describes itself as: An all-in-one local AI Agent workspace with a fully self-developed stack. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Planning
  • Tasks that involve User stories

Example prompts

  • “Use the notion-spec-to-implementation skill to turn product or tech specs into concrete Notion tasks that Claude code can implement”
  • “/notion-spec-to-implementation”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Find the specification
  2. Fetch and analyze specification
  3. Create implementation plan
  4. Create implementation plan page
  5. Find task database
  6. Create implementation tasks
  7. Begin implementation
  8. Track progress

What it can do on your machine

Read from SKILL.md and the folder at commit 9c64865. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Notion Spec To Implementation loads about 2.2k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 648 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rongxinzy/RongxinAI at commit 9c64865, republished under its AGPL-3.0 licence (© rongxinzy). 648 words, ~2,158 tokens.

Download SKILL.mdSave it as .claude/skills/notion-spec-to-implementation/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
notion-spec-to-implementation
description
Turns 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.

Spec to Implementation

Transforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.

Quick Start

When asked to implement a specification:

  1. Find spec: Use Notion:notion-search to locate specification page
  2. Fetch spec: Use Notion:notion-fetch to read specification content
  3. Extract requirements: Parse and structure requirements from spec
  4. Create plan: Use Notion:notion-create-pages for implementation plan
  5. Find task database: Use Notion:notion-search to locate tasks database
  6. Create tasks: Use Notion:notion-create-pages for individual tasks in task database
  7. Track progress: Use Notion:notion-update-page to log progress and update status

Implementation Workflow

Step 1: Find the specification
1. Search for spec:
   - Use Notion:notion-search with spec name or topic
   - Apply filters if needed (e.g., created_date_range, teamspace_id)
   - Look for spec title or keyword matches
   - If not found or ambiguous, ask user for spec URL/ID

Example searches:
- "User Authentication spec"
- "Payment Integration specification"
- "Mobile App Redesign PRD"
Step 2: Fetch and analyze specification
1. Fetch spec page:
   - Use Notion:notion-fetch with spec URL/ID from search results
   - Read full content including requirements, design, constraints

2. Parse specification:
   - Identify functional requirements
   - Note non-functional requirements (performance, security, etc.)
   - Extract acceptance criteria
   - Identify dependencies and blockers

See reference/spec-parsing.md for parsing patterns.

Step 3: Create implementation plan
1. Break down into phases/milestones
2. Identify technical approach
3. List required tasks
4. Estimate effort
5. Identify risks

Use implementation plan template (see [reference/standard-implementation-plan.md](reference/standard-implementation-plan.md) or [reference/quick-implementation-plan.md](reference/quick-implementation-plan.md))
Step 4: Create implementation plan page
Use Notion:notion-create-pages:
- Title: "Implementation Plan: [Feature Name]"
- Content: Structured plan with phases, tasks, timeline
- Link back to original spec
- Add to appropriate location (project page, database)
Step 5: Find task database
1. Search for task database:
   - Use Notion:notion-search to find "Tasks" or "Task Management" database
   - Look for engineering/project task tracking system
   - If not found or ambiguous, ask user for database location

2. Fetch database schema:
   - Use Notion:notion-fetch with database URL/ID
   - Get property names, types, and options
   - Identify correct data source from <data-source> tags
   - Note required properties for new tasks
Step 6: Create implementation tasks
For each task in plan:
1. Create task in task database using Notion:notion-create-pages
2. Use parent: { data_source_id: 'collection://...' }
3. Set properties from schema:
   - Name/Title: Task description
   - Status: To Do
   - Priority: Based on criticality
   - Related Tasks: Link to spec and plan
4. Add implementation details in content

See reference/task-creation.md for task patterns.

Step 7: Begin implementation
1. Update task status to "In Progress"
2. Add initial progress note
3. Document approach and decisions
4. Link relevant resources
Step 8: Track progress
Regular updates:
1. Update task properties (status, progress)
2. Add progress notes with:
   - What's completed
   - Current focus
   - Blockers/issues
3. Update implementation plan with milestone completion
4. Link to related work (PRs, designs, etc.)

See reference/progress-tracking.md for tracking patterns.

Spec Analysis Patterns

Functional Requirements: User stories, feature descriptions, workflows, data requirements, integration points

Non-Functional Requirements: Performance targets, security requirements, scalability needs, availability, compliance

Acceptance Criteria: Testable conditions, user validation points, performance benchmarks, completion definitions

See reference/spec-parsing.md for detailed parsing techniques.

Implementation Plan Structure

Plan includes: Overview → Linked Spec → Requirements Summary → Technical Approach → Implementation Phases (Goal, Tasks checklist, Estimated effort) → Dependencies → Risks & Mitigation → Timeline → Success Criteria

See reference/standard-implementation-plan.md for full plan template.

Task Breakdown Patterns

By Component: Database, API endpoints, frontend components, integration, testing By Feature Slice: Vertical slices (auth flow, data entry, report generation) By Priority: P0 (must have), P1 (important), P2 (nice to have)

Progress Logging

Daily Updates (active work): Add progress note with completed items, current focus, blockers Milestone Updates (major progress): Update plan checkboxes, add milestone summary, adjust timeline Status Changes (task transitions): Update properties (In Progress → In Review → Done), add completion notes, link deliverables

Progress Format: Date heading → Completed → In Progress → Next Steps → Blockers → Notes

See reference/progress-tracking.md for detailed patterns.

Linking Spec to Implementation

Forward Links: Update spec page with "Implementation" section linking to plan and tasks Backward Links: Reference spec in plan and tasks with "Specification" section Bidirectional Traceability: Maintain both directions for easy tracking

Implementation Status Tracking

Plan Status: Update with phase completion (✅ Complete, 🔄 In Progress %, ⏳ Not Started) and overall percentage Task Aggregation: Query task database by plan ID to generate summary (complete, in progress, blocked, not started)

Show full SKILL.md (256 more words)Show less

Handling Spec Changes

Detection: Fetch updated spec → compare with plan → identify new requirements → assess impact Propagation: Update plan → create new tasks → update affected tasks → add change note → notify via comments Change Log: Track spec evolution with date, what changed, and impact

Common Patterns

Feature Flag: Backend (behind flag) → Testing → Frontend (flagged) → Internal rollout → External rollout Database Migration: Schema design → Migration script → Staging test → Production migration → Validation API Development: API design → Backend implementation → Testing & docs → Client integration → Deployment

Best Practices

  1. Always link spec and implementation: Maintain bidirectional references
  2. Break down into small tasks: Each task should be completable in 1-2 days
  3. Extract clear acceptance criteria: Know when "done" is done
  4. Identify dependencies early: Note blockers in plan
  5. Update progress regularly: Daily notes for active work
  6. Track changes: Document spec updates and their impact
  7. Use checklists: Visual progress indicators help everyone
  8. Link deliverables: PRs, designs, docs should link back to tasks

Advanced Features

For additional implementation patterns and techniques, see the reference files in reference/.

Common Issues

"Can't find spec": Use Notion:notion-search with spec name/topic, try broader terms, or ask user for URL "Multiple specs found": Ask user which spec to implement or show options "Can't find task database": Search for "Tasks" or "Task Management", or ask user for database location "Spec unclear": Note ambiguities in plan, create clarification tasks "Requirements conflicting": Document conflicts, create decision task "Scope too large": Break into smaller specs/phases

Examples

See examples/ for complete workflows:

© rongxinzy, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files in MCPs/notion/skills/spec-to-implementation of rongxinzy/RongxinAI.

  • SKILL.md
  • evaluations/README.md
  • evaluations/basic-spec-implementation.json
  • evaluations/spec-to-tasks.json
  • examples/api-feature.md
  • examples/database-migration.md
  • examples/ui-component.md
  • reference/milestone-summary-template.md
  • reference/progress-tracking.md
  • reference/progress-update-template.md
  • reference/quick-implementation-plan.md
  • reference/spec-parsing.md
  • reference/standard-implementation-plan.md
  • reference/task-creation-template.md
  • reference/task-creation.md

Open the folder on GitHubat commit 9c64865

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in rongxinzy/RongxinAI, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Notion Spec To Implementation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Notion Spec To Implementation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Notion Spec To Implementation this skillrongxinzy/RongxinAI1542 repos~2.2kAutomated safety check: PassAGPL-3.0
Gen Planalibaba/atrex-kernel-agent168—~3.4kAutomated safety check: PassMIT
Code Task Generatormikeyobrien/ralph-orchestrator3.2k—~1.6kAutomated safety check: PassMIT
Autospec Tasksariel-frischer/autospec144—~2.5kAutomated safety check: PassMIT
Factory Queuetikalk/adlc-team-skills141—~1.3kAutomated safety check: PassMIT
App Buildermicrosoft/power-platform-skills984—~13kAutomated safety check: NotesMIT

Similar skills

  • Gen Plan

    alibaba/atrex-kernel-agent

    Generate a structured implementation plan from an evidence draft.

    168 GitHub stars~3.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Code Task Generator

    mikeyobrien/ralph-orchestrator

    Generates structured .code-task.md files from descriptions or PDD implementation plans.

    3.2k GitHub stars~1.6k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Autospec Tasks

    ariel-frischer/autospec

    Generate YAML task breakdown from implementation plan. An agent skill from ariel-frischer/autospec.

    144 GitHub stars~2.5k tokensUpdated 13 days ago
    Agent WorkflowsAuto-check passed
  • Factory Queue

    tikalk/adlc-team-skills

    A skill your agent uses when managing mission brief intake — triage, AI-assisted advisory scoring, gating label stamping, and milestones or epics generation (plan mode).

    141 GitHub stars~1.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • App Builder

    microsoft/power-platform-skills

    Official

    Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business…

    984 GitHub stars~13k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Feature Planning

    HybridAIOne/hybridclaw

    Break features into implementation plans, acceptance criteria, and sequenced tasks.

    159 GitHub stars~720 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from rongxinzy/RongxinAI

All 94 skills in this repo
  • SaaS Metrics Coach

    rongxinzy/RongxinAI

    SaaS financial health advisor. An agent skill from rongxinzy/RongxinAI.

    154 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Churn Prevention

    rongxinzy/RongxinAI

    Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.

    154 GitHub starsUsed in 3 repos~2.6k tokens
    Auto-check passed
  • Presentation Studio

    rongxinzy/RongxinAI

    The only skill for creating a new PowerPoint deck. An agent skill from rongxinzy/RongxinAI.

    154 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Zhiyuan Expert Manager

    rongxinzy/RongxinAI

    ZhiYuan Agent expert package lifecycle manager for the pi engine.

    154 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Ziwei Doushu

    rongxinzy/RongxinAI

    Professional Ziwei Doushu consultation skill with an offline calculation engine.

    154 GitHub stars~746 tokensUpdated yesterday
    Auto-check passed
  • Lark Mail

    rongxinzy/RongxinAI

    飞书邮箱:Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等;use for mail/email intent only.

    154 GitHub starsUsed in 3 repos~4.1k tokens
    Auto-check: warnings

Works with

Questions about Notion Spec To Implementation

What does Notion Spec To Implementation do?

Turns product or tech specs into concrete Notion tasks that Claude code can implement. Notion Spec To Implementation is an agent skill from rongxinzy/RongxinAI. Turns product or tech specs into concrete Notion tasks that Claude code can implement.

When should I use Notion Spec To Implementation?

Notion Spec To Implementation fits situations like: tasks that involve Planning; tasks that involve User stories.

How do I install Notion Spec To Implementation in Claude Code?

Run `npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a claude-code`. Or copy the skill folder (MCPs/notion/skills/spec-to-implementation in rongxinzy/RongxinAI) into .claude/skills/notion-spec-to-implementation in your project. Claude Code loads it when a task matches its description.

How do I install Notion Spec To Implementation in Codex?

Run `npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a codex`. Or copy the skill folder (MCPs/notion/skills/spec-to-implementation in rongxinzy/RongxinAI) into .agents/skills/notion-spec-to-implementation in your project. Codex loads it when a task matches its description.

Can I use Notion Spec To Implementation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notion-spec-to-implementation, .gemini/skills/notion-spec-to-implementation, .github/skills/notion-spec-to-implementation and .opencode/skills/notion-spec-to-implementation in your project.

What does Notion Spec To Implementation need to run?

SKILL.md names no scripts, command-line tools or credentials: Notion Spec To Implementation is instructions for the agent only.

Does Notion Spec To Implementation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Notion Spec To Implementation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Notion Spec To Implementation use?

Notion Spec To Implementation is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Notion Spec To Implementation use?

About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Notion Spec To Implementation?

Skills that share tags, products or a category with Notion Spec To Implementation: Gen Plan (alibaba/atrex-kernel-agent, 168 stars), Code Task Generator (mikeyobrien/ralph-orchestrator, 3.2k stars), Autospec Tasks (ariel-frischer/autospec, 144 stars) and Factory Queue (tikalk/adlc-team-skills, 141 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Notion Spec To Implementation?

rongxinzy (a GitHub organization) maintains it in rongxinzy/RongxinAI, which has 154 GitHub stars. The repository holds 94 skills in this directory. The repository was last updated on October 10, 2026.

Source: rongxinzy/RongxinAI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.