Index of every page on this site: llms.txt
All skills
makenotion avatar

/spec-to-implementation

@016c74f official
Run it yourself

Converts Notion product or technical specs into implementation plans, linked tasks, and evidence-based progress updates. Use for planning or implementing a spec, creating tasks from requirements, or reconciling implementation with spec changes.

  • 20 files
  • 65.3 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/makenotion/claude-code-notion-plugin/spec-to-implementation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplesui-component.md

≈418 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Example: UI Component Implementation

User Request: "Implement the new search component from the design spec"

Workflow

1. Find Spec

Notion:notion-search
query: "search component design spec"

Found: "Global Search Redesign Spec"

2. Fetch & Parse Spec

Notion:notion-fetch

Requirements:

  • Instant search with debounced API calls
  • Keyboard navigation (↑↓ arrows, Enter, Esc)
  • Recent searches history
  • Result categories (pages, people, files)
  • Mobile responsive
  • Accessibility (ARIA labels, screen reader)

3. Create Implementation Plan

Notion:notion-create-pages

Plan phases:

  • Phase 1: Base component structure
  • Phase 2: API integration & debouncing
  • Phase 3: Keyboard navigation
  • Phase 4: Recent searches
  • Phase 5: Polish & accessibility

4. Create Tasks

Notion:notion-create-pages (7 tasks)

Tasks:

  1. Create SearchInput component
  2. Implement useDebounce hook
  3. Add keyboard navigation
  4. LocalStorage for recent searches
  5. Result categorization UI
  6. Accessibility audit
  7. Mobile responsive styling

5. Implement & Track

As each task completed, updated status and added progress notes with screenshots and implementation details.

Key Outputs

Implementation Plan (linked to design spec) 7 Component Tasks (in Engineering Tasks database) Progress Updates (with code snippets and demo links)

Success Factors

  • Clear component breakdown
  • Separated concerns (logic, UI, accessibility)
  • Each task had acceptance criteria
  • Referenced design spec throughout
  • Included accessibility from start, not afterthought
  • Tracked progress with visual updates

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 016c74f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for makenotion/claude-code-notion-plugin/spec-to-implementation