メニュー
Use wipnote analytics to make smart work prioritization decisions. Activate when recommending work, finding bottlenecks, assessing risks, or analyzing project impact.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | strategic-planning |
| description | Use wipnote analytics to make smart work prioritization decisions. Activate when recommending work, finding bottlenecks, assessing risks, or analyzing project impact. |
Trigger keywords:
Trigger situations:
CLI reference: Run wipnote help for available commands. Key commands:
wipnote status — project overviewwipnote find features --status in-progress — active workwipnote recommend — AI-recommended next workwipnote provides analytics that consider:
# 1. What should I work on? (recommendations)
wipnote analytics summary
# 2. What's blocking progress?
wipnote analytics summary
# 3. Project snapshot (status + WIP)
wipnote snapshot --summary
# 4. Find in-progress work
wipnote find features --status in-progress
wipnote analytics summaryFind tasks that block the most downstream work.
wipnote analytics summary
Use when:
wipnote analytics summaryGet scored recommendations considering all factors.
wipnote analytics summary
Scoring factors:
wipnote find features --status todoFind tasks that can run concurrently (no dependencies).
# All todo features
wipnote find features --status todo
# All in-progress
wipnote find features --status in-progress
Use when:
wipnote snapshot --summaryProject health and status overview.
wipnote snapshot --summary
Use when:
# Get project status overview
wipnote status
wipnote snapshot --summary
wipnote analytics summary
# Find what's causing the block
wipnote analytics summary
wipnote find features --status blocked
# Check what's ready (no dependencies)
wipnote analytics summary
wipnote find features --status todo
# See everything by status
wipnote find features --status in-progress
wipnote find features --status todo
wipnote find bugs --status open
Use CLI analytics to inform planning decisions:
# Get full picture before planning
wipnote analytics summary
wipnote snapshot --summary
# Use wipnote plan generate to create formal plans
wipnote plan generate <track-id>
# What's blocking us?
wipnote analytics summary
# What should I do?
wipnote analytics summary
# Project snapshot
wipnote snapshot --summary
# Check status
wipnote status
# Find in-progress work
wipnote find features --status in-progress
# Find todo work (parallelizable candidates)
wipnote find features --status todo
Run wipnote recommend [--top N] (default N=5) for scored recommendations:
wipnote recommend --top 5
After presenting output, analyze whether the top recommendations can run in parallel:
/wipnote:execute for parallel dispatchPropose next action:
/wipnote:execute (parallel)/wipnote:plan <id>wipnote orchestration patterns for AI-assisted development. Use when working on code in an wipnote project — provides delegation patterns, model selection, quality gates, and work tracking guidance. Activate when planning work, delegating to agents, debugging, building features, or managing tasks.
wipnote orchestration patterns for AI-assisted development. Use when working on code in an wipnote project — provides delegation patterns, model selection, quality gates, and work tracking guidance. Activate when planning work, delegating to agents, debugging, building features, or managing tasks.
wipnote orchestration patterns for AI-assisted development. Use when working on code in an wipnote project — provides delegation patterns, model selection, quality gates, and work tracking guidance. Activate when planning work, delegating to agents, debugging, building features, or managing tasks.
Plan development work using a triage-gated, blocks-first interview. Classify scope as trivial/standard/complex, then run 0/3/4 staged interview rounds through the current harness native ask-user tool when available, or plain conversation when it is not. Each stage elicits the VISUAL block first (file-tree, api-endpoint, data-model, wireframe/diagram) and derives the prose slice fields (what/why/done_when) from it — blocks are authored inline as the YAML is built, not in a post-pass. Produces slice-card YAML with grounded visual blocks and visible research provenance for external claims; pauses for human review; promotes approved slices to features. Use when asked to plan, create a development plan, or build a feature with design clarity first.
SECONDARY enrichment path — add or revise structured visual blocks (data-model, api-endpoint, file-tree, wireframe, diagram, tabs) on an EXISTING wipnote plan. Use for legacy plans drafted before blocks-first existed, or for ad-hoc later block additions/revisions — NOT for primary planning. New plans get blocks authored inline during the wipnote:plan interview (blocks-first); only reach for this skill when a plan already exists and needs blocks added or changed after the fact. Reads the live block catalog from wipnote plan blocks, adds grounded blocks to slices, regenerates the plan HTML, and links to the dashboard.
Generate a grounded visual recap for a work item, git range, or session. Runs wipnote recap to produce a self-contained HTML artifact grounded in the real diff, reads the artifact, writes an outcome narrative (secrets redacted), and links to the dashboard recap URL. Use when asked to recap, summarize, or visualize completed work.