tasks-plan
Create an implementation plan from a Notion task or specification. Breaks down requirements into actionable steps with estimates and dependencies.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- tasks-plan
- description
- Create an implementation plan from a Notion task or specification. Breaks down requirements into actionable steps with estimates and dependencies.
03 SKILL.md 正文
Plan Task Implementation
Create a detailed implementation plan from a Notion task or specification page.
Input
The user provides a Notion page URL containing a task or specification.
Workflow
1. Fetch the specification
Use the Notion MCP tools to:
- Get the page content including requirements, acceptance criteria, and constraints
- Read any linked pages or references for additional context
- Identify dependencies and blockers
2. Analyze requirements
Extract and categorize:
- Functional requirements (what the system should do)
- Non-functional requirements (performance, security, etc.)
- Acceptance criteria (how to verify completion)
- Dependencies (what needs to happen first)
3. Break down into tasks
Create a structured implementation plan:
- Group work into logical phases or milestones
- Break each phase into specific, actionable tasks
- Identify the technical approach for each task
- Note any risks or uncertainties
4. Create the plan in Notion
Use the Notion MCP to create a new page with:
- Title: "Implementation Plan: [Feature Name]"
- Overview section summarizing the approach
- Phases with task checklists
- Dependencies and risks sections
- Link back to the original specification
5. Optionally create tasks
If the user has a task database, offer to create individual task items for each step in the plan.
Output Format
The plan should include:
- Overview: Brief summary of what will be built
- Specification Link: Reference to the source document
- Technical Approach: High-level architecture decisions
- Phases: Numbered phases with task checklists
- Dependencies: What needs to be in place first
- Risks: Potential issues and mitigations
04 同仓库更多 Skills
business-data
暂无简介
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
workflow
Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.