skilld
All skills
openai avatar

/notion-spec-to-implementation

@136d58a official
by openaiopenai/skills28k stars
1,891

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/notion-spec-to-implementation

This session only. Nothing lands on disk.

referencestandard-implementation-plan.md

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

Standard Implementation Plan Template

Use this template for most feature implementations.

# Implementation Plan: [Feature Name]

## Overview
[1-2 sentence feature description and business value]

## Linked Specification
<mention-page url="...">Original Specification</mention-page>

## Requirements Summary

### Functional Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

### Non-Functional Requirements
- **Performance**: [Targets]
- **Security**: [Requirements]
- **Scalability**: [Needs]

### Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

## Technical Approach

### Architecture
[High-level architectural decisions]

### Technology Stack
- Backend: [Technologies]
- Frontend: [Technologies]
- Infrastructure: [Technologies]

### Key Design Decisions
1. **[Decision]**: [Rationale]
2. **[Decision]**: [Rationale]

## Implementation Phases

### Phase 1: Foundation (Week 1)
**Goal**: Set up core infrastructure

**Tasks**:
- [ ] <mention-page url="...">Database schema design</mention-page>
- [ ] <mention-page url="...">API scaffolding</mention-page>
- [ ] <mention-page url="...">Authentication setup</mention-page>

**Deliverables**: Working API skeleton
**Estimated effort**: 3 days

### Phase 2: Core Features (Week 2-3)
**Goal**: Implement main functionality

**Tasks**:
- [ ] <mention-page url="...">Feature A implementation</mention-page>
- [ ] <mention-page url="...">Feature B implementation</mention-page>

**Deliverables**: Core features working
**Estimated effort**: 1 week

### Phase 3: Integration & Polish (Week 4)
**Goal**: Complete integration and refinement

**Tasks**:
- [ ] <mention-page url="...">Frontend integration</mention-page>
- [ ] <mention-page url="...">Testing & QA</mention-page>

**Deliverables**: Production-ready feature
**Estimated effort**: 1 week

## Dependencies

### External Dependencies
- [Dependency 1]: [Status]
- [Dependency 2]: [Status]

### Internal Dependencies
- [Team/component dependency]

### Blockers
- [Known blocker] or None currently

## Risks & Mitigation

### Risk 1: [Description]
- **Probability**: High/Medium/Low
- **Impact**: High/Medium/Low
- **Mitigation**: [Strategy]

### Risk 2: [Description]
- **Probability**: High/Medium/Low
- **Impact**: High/Medium/Low
- **Mitigation**: [Strategy]

## Timeline

| Milestone | Target Date | Status |
|-----------|-------------|--------|
| Phase 1 Complete | [Date] | ⏳ Planned |
| Phase 2 Complete | [Date] | ⏳ Planned |
| Phase 3 Complete | [Date] | ⏳ Planned |
| Launch | [Date] | ⏳ Planned |

## Success Criteria

### Technical Success
- [ ] All acceptance criteria met
- [ ] Performance targets achieved
- [ ] Security requirements satisfied
- [ ] Test coverage > 80%

### Business Success
- [ ] [Business metric 1]
- [ ] [Business metric 2]

## Resources

### Documentation
- <mention-page url="...">Design Doc</mention-page>
- <mention-page url="...">API Spec</mention-page>

### Related Work
- <mention-page url="...">Related Feature</mention-page>

## Progress Tracking

[This section updated regularly]

### Phase Status
- Phase 1: ⏳ Not Started
- Phase 2: ⏳ Not Started
- Phase 3: ⏳ Not Started

**Overall Progress**: 0% complete

### Latest Update: [Date]
[Brief status update]

Source: SKILL.md on GitHub

Third-party checks

2 warnings16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides templates and workflows to translate Notion specifications into actionable implementation plans and tasks. It includes a few security considerations regarding the ingestion of external data from user-controlled documents, which are standard for automation and parsing workflows.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    6/17 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

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

Last checked against GitHub 2 months ago.

Activeupdated 10 months ago

Capability

Other metadata
metadata
{
  "short-description": "Turn Notion specs into implementation plans, tasks, and progress tracking"
}

Topics

  • notion
  • project-management
  • task-tracking
  • prd
  • implementation-planning
  • workflow
  • notion-mcp

README badge

README badge for openai/skills/notion-spec-to-implementation

What it does

Converts a Notion spec document into a linked implementation plan with tasks and status tracking, using Notion MCP calls to search, fetch, create pages, and update progress. Targets teams using Notion for PRDs and feature specs who want to automate plan generation and task creation from written requirements.

Generated from the current SKILL.md.

Frequently asked

Does this skill work with Notion MCP?
Yes. It requires the Notion MCP to be installed and authenticated via OAuth. If the MCP is not connected, the skill includes setup steps to add it and log in.
Can I use this skill for any kind of spec, or only certain types?
The skill works for any spec stored in Notion. It includes both quick and full implementation plan templates, so you can adapt the depth to simple changes or multi-phase features.
What Notion operations does this skill perform?
It searches and fetches specs, creates plan and task pages, updates pages with links and progress, and manages relations between spec, plan, and task artifacts.
Does this skill automatically generate task acceptance criteria?
No. The skill provides templates and patterns (in reference/task-creation-template.md) to guide task content, but you compose the acceptance criteria based on the spec requirements.

Generated from the current SKILL.md. These answers refresh after source changes.