lidge-jun/notion-spec-to-implementation
notion-spec-to-implementation/SKILL.md
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
$ install --global
skillsauthnpx skillsauth add lidge-jun/cli-jaw-skills notion-spec-to-implementationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:44 AM142.9s1 file scanned
SKILL.md
- name:
- notion-spec-to-implementation
- description:
- Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
- short-description:
- Turn Notion specs into implementation plans, tasks, and progress tracking
Spec to Implementation
Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Notion MCP setup (only if MCP calls fail)
codex mcp add notion --url https://mcp.notion.com/mcp- Set
[features].rmcp_client = trueinconfig.toml codex mcp login notion— then restart Codex.
Rules
1) Read the spec
- Search with
Notion:notion-search; if multiple hits, ask the user which to use. - Fetch with
Notion:notion-fetch. Extract: requirements, acceptance criteria, constraints, priorities. - Record gaps and assumptions in a clarifications block before proceeding. Why: unrecorded assumptions cause scope drift during implementation.
2) Create the plan
- Simple change (single component, no cross-team dependency) → single-page plan.
- Multi-phase feature or migration → phased plan with milestones.
- Create via
Notion:notion-create-pages. Include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria.
3) Create tasks
- Find the task database via
Notion:notion-search→Notion:notion-fetchto confirm schema and required properties. - Size to 1–2 days per task. Why: tasks larger than 2 days hide progress and make blockers invisible; smaller than 1 day creates overhead that outweighs tracking value.
- Each task must have: action-verb title, context sentence, acceptance criteria, dependencies, and relations to spec + plan.
- Set properties: status, priority, due date/story points/assignee when provided.
4) Link artifacts
- Plan links to spec; each task links to both plan and spec.
- Optionally add an "Implementation" section in the spec pointing to the plan via
Notion:notion-update-page.
5) Track progress
- Update task status and plan checklists as work progresses. Note blockers and decisions.
- Post milestone summaries when closing a phase.
Related Skills
lidge-jun/structured-renderers
development
VerifiedTrustedCommunity
Native Web UI structured renderer schemas for compose-block drafts, search-results cards, dataframe tables, chart-json charts, and diff output
4SKILL.mdUpdated Jun 12, 2026
lidge-jun/search
tools
VerifiedTrustedCommunity
Unified search hub. Route any web/real-time/X lookup through a 4-tier escalation: built-in web search → cli-jaw browser CDP → progrok Grok OAuth → web-ai (Grok Expert / GPT Pro). Use for: search, 검색, web search, latest news, real-time info, X/Twitter, fact lookup, deep research.
4SKILL.mdUpdated Jun 9, 2026
lidge-jun/dev-uiux-design
development
VerifiedTrustedCommunity
UI/UX intent discovery, design vocabulary, product personalities, UX state patterns, typography line break judgment, favicon/product logo design, and logo trust section design. Use when user design direction is vague, when building onboarding/empty/error states, when setting up favicons or product logos, or when referencing a product aesthetic.
4SKILL.mdUpdated Jun 8, 2026
lidge-jun/dev-architecture
development
VerifiedTrustedCommunity
Canonical owner of module boundary rules, circular dependency detection/prevention, implicit coupling taxonomy, barrel/re-export discipline, and boundary-only defensive programming. Referenced by dev, dev-code-reviewer, dev-backend, dev-frontend stubs.
4SKILL.mdUpdated Jun 8, 2026