メニュー
Plane.so project management interface via direct API scripts. Use when user says 'plane', 'check plane', 'update plane', 'GP-42', 'plane status', 'sync to plane', 'look up task', or any Plane-related project management action.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
End-of-conversation shipping and review workflow. Use when the user says wrap up, close out, end session, ship this, commit and push, prepare handoff, or asks for a session closeout. Runs a scheduler-safe preflight, verifies work, commits and pushes specific files when appropriate, captures open loops and improvement candidates, and ends with a clear handoff.
Software development end-to-end: scope -> design -> plan -> execute -> deploy. Merges scope, writing-plans, executing-plans, and subagent-driven-development. Use when the user says 'build', 'implement', 'code', 'write a script', 'create a feature', or when /think chains here after identifying a concrete software deliverable.
Structured debugging methodology that finds root causes before attempting fixes. Reproduces issues, traces data flow, forms hypotheses, and tests one variable at a time. Use when encountering any bug, test failure, unexpected behavior, or error message. Triggers on 'debug', 'fix this bug', 'why is this failing', 'test failure', 'error', or any unexpected behavior. Do NOT use for feature requests (use /build) or general code questions.
Personal finance planning system for initial setup (interview), full reviews, and quick analysis. Tracks net worth, runway, spending, taxes, investments, and retirement projections. Generates an HTML dashboard. Triggers on 'financial advisor', 'analyze my finances', 'review my finances', 'what's my runway', 'look at these statements', or when financial documents are dropped. Do NOT use for business revenue analysis or general math questions.
Present the daily operational briefing and start-of-day context. Use when the user says "good morning", "morning briefing", "what's today look like", "what do I have today", "morning rundown", "what's on my plate", "start of day", "weekly review", "weekly briefing", or "give me the weekly". Do NOT activate for casual mid-conversation "good morning" greetings when already deep in a task.
Find posts where @[your-handle] tags @builtwithjules, draft replies, post approved ones as @builtwithjules.
| name | plane |
| effort | medium |
| description | Plane.so project management interface via direct API scripts. Use when user says 'plane', 'check plane', 'update plane', 'GP-42', 'plane status', 'sync to plane', 'look up task', or any Plane-related project management action. |
Comprehensive interface to the Plane Cloud workspace ([your-workspace-slug], project Grand Plan).
All Plane operations use Python scripts calling the REST API via curl. No MCP server dependency — works in interactive and batch contexts.
| Operation | Script |
|---|---|
| List items, cycles, modules | plane_list.py items, plane_list.py cycles, plane_list.py modules |
| List items in a module | plane_list.py module-items "Pending Review" |
| Filter by state/due date | plane_list.py items --state todo,in_progress --due-within 7 |
| Create item (+ add to module) | plane_create.py "Title" --module "Pending Review" |
| Get item by identifier (GP-42) | plane_lookup.py GP-42 |
| Search items by keyword | plane_search.py "keyword" |
| Pull Plane status → markdown | plane_pull.py [--apply] |
| Compare local vs Plane | plane_compare.py [--diff-only] [--module slug] |
All scripts require PLANE_API_KEY. On Mac, inject at call time:
# Lookup by identifier
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_lookup.py GP-42
# Search
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_search.py "authentication" --state todo
# Push: markdown -> Plane (dry-run by default, --apply for live)
python3 .claude/skills/plane/scripts/plane_sync.py # dry-run
python3 .claude/skills/plane/scripts/plane_sync.py --apply # live changes
# Pull: Plane -> markdown (dry-run by default, --apply writes with backup)
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_pull.py # dry-run
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_pull.py --apply # live (backs up to .plane-pull-backup/)
# Compare: side-by-side diff (read-only)
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_compare.py # full table
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_compare.py --diff-only # only mismatches
PLANE_API_KEY=$(op item get "Plane API" --vault "Dev Secrets" --fields label="API Key" --reveal) \
python3 .claude/skills/plane/scripts/plane_compare.py --module infrastructure # filter by module
The sync script auto-injects credentials via op if PLANE_API_KEY is not set.
See references/our-workspace.md for all IDs, states, modules, labels, and conventions.
[your-workspace-slug]Grand Plan (UUID: 8238b353-5e87-4b72-b199-fec061be8b98)GP[YOUR_USER_ID]See references/patterns.md for:
Description [TASK-ID]MCP server is Mac-only (interactive Claude Code sessions). It launches via start-plane-mcp.sh, which resolves the API key from 1Password using the OP_SERVICE_ACCOUNT_TOKEN (set in ~/.zshrc). Batch jobs use gap scripts with PLANE_API_KEY from macOS Keychain (security find-generic-password -s plane-api-key).
references/our-workspace.md -- IDs, states, modules, labelsreferences/api-reference.md -- Condensed endpoint referencereferences/mcp-tools.md -- MCP server tool catalog (populate after smoke test)references/patterns.md -- Learned API patterns and gotchas