Gen Plan
alibaba/atrex-kernel-agent
Generate a structured implementation plan from an evidence draft.
Turns product or tech specs into concrete Notion tasks that Claude code can implement.
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "notion-spec-to-implementation" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementation into .claude/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/MCPs/notion/skills/spec-to-implementation .agents/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementation into .agents/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/MCPs/notion/skills/spec-to-implementation .cursor/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementation into .cursor/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rongxinzy/RongxinAI.git --path MCPs/notion/skills/spec-to-implementation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/MCPs/notion/skills/spec-to-implementation .gemini/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementation into .gemini/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .github/skills && cp -r skills-src/MCPs/notion/skills/spec-to-implementation .github/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementation into .github/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rongxinzy/RongxinAI --skill notion-spec-to-implementation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rongxinzy/RongxinAI notion-spec-to-implementation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/MCPs/notion/skills/spec-to-implementation .opencode/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/spec-to-implementation into .opencode/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
notion-spec-to-implementationTurns 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. 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.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9c64865. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from rongxinzy/RongxinAI at commit 9c64865, republished under its AGPL-3.0 licence (© rongxinzy). 648 words, ~2,158 tokens.
.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.Transforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.
When asked to implement a specification:
Notion:notion-search to locate specification pageNotion:notion-fetch to read specification contentNotion:notion-create-pages for implementation planNotion:notion-search to locate tasks databaseNotion:notion-create-pages for individual tasks in task databaseNotion:notion-update-page to log progress and update status1. 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"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 blockersSee reference/spec-parsing.md for parsing patterns.
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))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)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 tasksFor 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 contentSee reference/task-creation.md for task patterns.
1. Update task status to "In Progress"
2. Add initial progress note
3. Document approach and decisions
4. Link relevant resourcesRegular 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.
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.
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.
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)
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.
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
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)
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
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
For additional implementation patterns and techniques, see the reference files in reference/.
"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
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
SKILL.md and 14 other files in MCPs/notion/skills/spec-to-implementation of rongxinzy/RongxinAI.
Open the folder on GitHubat commit 9c64865
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Notion Spec To Implementation this skillrongxinzy/RongxinAI | 154 | 2 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Gen Planalibaba/atrex-kernel-agent | 168 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Code Task Generatormikeyobrien/ralph-orchestrator | 3.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Autospec Tasksariel-frischer/autospec | 144 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Factory Queuetikalk/adlc-team-skills | 141 | — | ~1.3k | Automated safety check: Pass | MIT | |
| App Buildermicrosoft/power-platform-skills | 984 | — | ~13k | Automated safety check: Notes | MIT |
alibaba/atrex-kernel-agent
Generate a structured implementation plan from an evidence draft.
mikeyobrien/ralph-orchestrator
Generates structured .code-task.md files from descriptions or PDD implementation plans.
ariel-frischer/autospec
Generate YAML task breakdown from implementation plan. An agent skill from ariel-frischer/autospec.
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).
microsoft/power-platform-skills
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…
HybridAIOne/hybridclaw
Break features into implementation plans, acceptance criteria, and sequenced tasks.
rongxinzy/RongxinAI
SaaS financial health advisor. An agent skill from rongxinzy/RongxinAI.
rongxinzy/RongxinAI
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.
rongxinzy/RongxinAI
The only skill for creating a new PowerPoint deck. An agent skill from rongxinzy/RongxinAI.
rongxinzy/RongxinAI
ZhiYuan Agent expert package lifecycle manager for the pi engine.
rongxinzy/RongxinAI
Professional Ziwei Doushu consultation skill with an offline calculation engine.
rongxinzy/RongxinAI
飞书邮箱:Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等;use for mail/email intent only.
Works with
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.
Notion Spec To Implementation fits situations like: tasks that involve Planning; tasks that involve User stories.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Notion Spec To Implementation is instructions for the agent only.
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.
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.
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.
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.
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.
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.