Skip to content

Prat011/awesome-llm-skills / notion-spec-to-implementation

notion-spec-to-implementation

Unverified

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.

evaluations/basic-spec-implementation.json

View on GitHub
{
  "name": "Create Implementation Plan from Spec",
  "skills": ["spec-to-implementation"],
  "query": "Create an implementation plan for the User Authentication spec page",
  "expected_behavior": [
    "Step 1: Uses Notion:notion-search to find 'User Authentication spec' with keywords like 'User Authentication' or 'auth spec'",
    "Step 2: If not found or ambiguous, asks user for spec page URL/ID",
    "Step 3: Fetches spec page using Notion:notion-fetch with URL/ID from search results",
    "Step 4: Parses spec using patterns from reference/spec-parsing.md to extract requirements, acceptance criteria, constraints",
    "Step 5: Identifies functional requirements (user stories, features, workflows) and non-functional requirements (performance, security)",
    "Step 6: Creates implementation plan following structure from reference/templates.md",
    "Step 7: Includes sections: Overview, Linked Spec, Requirements Summary, Technical Approach, Implementation Phases",
    "Step 8: Breaks work into logical phases with Goal, Tasks checklist, Estimated effort per phase",
    "Step 9: Identifies dependencies and risks from spec content",
    "Step 10: Links plan back to original spec page using <mention-page url='...'>",
    "Step 11: Creates plan page using Notion:notion-create-pages with appropriate title (e.g., 'Implementation Plan: User Authentication')",
    "Step 12: Places plan appropriately (asks user or suggests under project/spec parent)"
  ],
  "success_criteria": [
    "Spec is found using Notion:notion-search before attempting to fetch (or user is asked for URL if not found)",
    "Spec is fetched using Notion:notion-fetch with correct URL/ID from search results",
    "Plan includes clear overview and spec link with mention-page tag",
    "Requirements are extracted from actual spec content (not generic) using spec-parsing patterns",
    "Work is broken into multiple phases (typically 3-5) following template structure",
    "Each phase has Goal, Tasks (as checkboxes), and Estimated effort",
    "Dependencies and risks sections are included with specific details from spec",
    "Plan follows Implementation Plan structure from reference/templates.md",
    "Success criteria or acceptance criteria from spec are referenced in plan",
    "Uses correct tool names and sequence: Notion:notion-search → Notion:notion-fetch → Notion:notion-create-pages"
  ]
}

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall