notion-spec-to-implementation
Audited by Runlayer on Feb 23, 2026
Malicious tool definition detected
Tool: SKILL.md [1/2] Description: --- 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.
Description: additional implementation patterns and techniques, see the reference files in [reference/](reference/).
Malicious tool definition detected
Tool: evaluations/README.md Description: # Spec to Implementation Skill Evaluations Evaluation scenarios for testing the Spec to Implementation skill across different Claude models.
Malicious tool definition detected
Tool: evaluations/basic-spec-implementation.json Description: { "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-fet
Malicious tool definition detected
Tool: evaluations/spec-to-tasks.json Description: { "name": "Create Tasks from Specification", "skills": ["spec-to-implementation", "task-manager"], "query": "Read the Payment Integration spec and create implementation tasks in our Tasks database", "expected_behavior": [ "Step 1: Uses Notion:notion-search to find Payment Integration spec or asks for URL", "Step 2: Fetches spec page using Notion:notion-fetch to read full content", "Step 3: Parses spec using reference/spec-parsing.md patterns to i
Malicious tool definition detected
Tool: examples/api-feature.md [1/2] Description: # Example: API Feature Implementation ## User Request > "Create an implementation plan for the User Profile API spec" ## Workflow Execution ### Step 1: Fetch Specification ``` Notion:notion-search query: "User Profile API spec" query_type: "internal" ``` Found: "User Profile API Specification" in Engineering Specs ``` Notion:notion-fetch id: "user-profile-api-spec-page-id" ``` ### Step 2: Parse Specification **Spec Content Extracted:** ```markdown
Tool: examples/api-feature.md [2/2] Description: testing - [ ] Handles 1000 concurrent users - [ ] All acceptance criteria met - [ ] Test coverage > 80% - [ ] Security scan passed - [ ] API documentation complete ### Business Success - [ ] User profile updates functional - [ ] Avatar uploads working reliably - [ ] Search returns relevant results in < 500ms - [ ] Zero critical bugs in first week ## Resources ### Documentation - <mention-page url="...">User Profile API Specification</mention-page>
Malicious tool definition detected
Tool: examples/database-migration.md Description: # Example: Database Migration Implementation **User Request**: "Plan and implement the database migration for user preferences schema" ## Workflow ### 1.
Malicious tool definition detected
Tool: examples/ui-component.md Description: # Example: UI Component Implementation **User Request**: "Implement the new search component from the design spec" ## Workflow ### 1.
Malicious tool definition detected
Tool: reference/milestone-summary-template.md Description: # Milestone Summary Template Use this when completing major phases or milestones.
Malicious tool definition detected
Tool: reference/progress-tracking.md [1/2] Description: # Progress Tracking ## Update Frequency ### Daily Updates For active implementation work: **What to update**: - Task status if changed - Add progress note to task - Update blockers **When**: - End of work day - After completing significant work - When encountering blockers ### Milestone Updates For phase/milestone completion: **What to update**: - Mark phase complete in plan - Add milestone summary - Update timeline if needed - Report to st
Tool: reference/progress-tracking.md [2/2] Description: rate: 95% - Bug count: 3 (2 minor, 1 cosmetic) - Performance: All targets met - Security: No issues found ``` ### Progress Metrics Quantitative progress: ```markdown ## Progress Metrics - Requirements implemented: 15/20 (75%) - Acceptance criteria met: 42/56 (75%) - Test cases passing: 128/135 (95%) - Code complete: 80% - Documentation: 60% ``` ## Stakeholder Communication ### Weekly Status Report ```markdown ## Weekly Status: [Week of Date
Malicious tool definition detected
Tool: reference/progress-update-template.md Description: # Progress Update Template Use this to update progress on implementation plans and tasks.
Malicious tool definition detected
Tool: reference/quick-implementation-plan.md Description: # Quick Implementation Plan Template For simpler features or small changes.
Malicious tool definition detected
Tool: reference/spec-parsing.md Description: # Specification Parsing ## Finding the Specification Before parsing, locate the spec page: ``` 1.
Malicious tool definition detected
Tool: reference/standard-implementation-plan.md Description: # Standard Implementation Plan Template Use this template for most feature implementations.
Malicious tool definition detected
Tool: reference/task-creation-template.md Description: # Task Creation Template When creating tasks from spec.
Malicious tool definition detected
Tool: reference/task-creation.md [1/2] Description: # Task Creation from Specs ## Finding the Task Database Before creating tasks, locate the task database: ``` 1.
Tool: reference/task-creation.md [2/2] Description: properties 2.