菜单
Publish implementation plans to Notion instead of local markdown. Use whenever creating an implementation plan, architecture plan, spike plan, migration plan, or any planning document. Replaces local docs/ output with a Notion page under the Planning docs page.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | plan-to-notion |
| description | Publish implementation plans to Notion instead of local markdown. Use whenever creating an implementation plan, architecture plan, spike plan, migration plan, or any planning document. Replaces local docs/ output with a Notion page under the Planning docs page. |
Publish implementation plans directly to Notion as child pages of the "Planning docs" page.
Config: Read config.json to get the planning_page_id.
Use this skill instead of writing local markdown whenever producing:
Do NOT write plans to local docs/ directories. Always publish to Notion.
Before writing content, fetch the Notion enhanced markdown spec:
FetchMcpResource: notion://docs/enhanced-markdown-spec
Use this spec for all content formatting.
Every plan page must use this structure. Skip sections that have no content, but always include Overview, Scope, Tasks, and Open Questions.
## Overview
One-paragraph summary of what this plan covers and why.
## Goals
- Goal 1
- Goal 2
## Non-Goals
- Explicitly out of scope item 1
## Scope
What parts of the codebase / system are affected.
| Area | Files / Modules | Impact |
|------|----------------|--------|
| ... | ... | ... |
## Approach
Narrative description of the implementation strategy. Include trade-offs considered and why this approach was chosen.
## Tasks
Ordered list of implementation steps. Each task should be actionable and independently mergeable where possible.
- [ ] Task 1 — description
- [ ] Task 2 — description
- [ ] Task 3 — description
## Risks & Mitigations
| Risk | Likelihood | Mitigation |
|------|-----------|------------|
| ... | ... | ... |
## Open Questions
- Question 1
- Question 2
## References
- Links to tickets, PRs, docs, Figma, Slack threads
config.json to get planning_page_idCallMcpTool: user-notiongusto / notion-create-pages
{
"parent": { "page_id": "<planning_page_id>" },
"pages": [{
"properties": { "title": "<Plan Title>" },
"content": "<plan content in Notion markdown>"
}]
}
Format: [Project/Feature] Implementation Plan
Examples:
When another skill (e.g. dev-workflow-start-work, investigate-create-doc) would normally produce a local planning document, this skill takes over the output step. The investigation / research phase stays the same — only the final write destination changes from local markdown to Notion.
Create a demo user and company on local Panda via curl. Authenticates against the local dev server, submits the demo account form, and returns login credentials. Use when the user asks to create a local user, demo account, demo company, or needs a test account on local Panda.
List and remove old git worktrees sorted by last activity. Shows when each worktree was last touched and lets the user pick which ones to remove. Also cleans up the associated local branch and AVD emulator if one exists. Use when the user says "cleanup worktrees", "remove worktrees", "delete old worktrees", "clean up branches", or "list worktrees".
Delete all Android emulators created by the build-android-app skill. Finds AVDs matching the {project}_{branch} naming convention, shuts down any that are running, and deletes them. Use when the user says "cleanup emulators", "delete emulators", "remove avds", or "clean up android emulators".
Build, install, and launch an Android app on an emulator after code changes. Auto-detects Gradle wrapper, build variant, application ID, and emulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on emulator", or when a workspace rule says to build after changes.
Build, install, and launch an iOS app on the Simulator after code changes. Auto-detects project file, scheme, bundle ID, and simulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on simulator", or when a workspace rule says to build after changes.
Create, delete, and manage iOS Simulator devices using xcrun simctl. Use when the user wants to create a simulator, delete a simulator, list simulators, reset a simulator, clone a device, rename a device, or manage simulator lifecycle (boot, shutdown, erase).