メニュー
ARCHIVED — Use wipnote skill instead. wipnote workflow combining session tracking, orchestration, and parallel coordination.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | wipnote-tracker |
| description | ARCHIVED — Use wipnote skill instead. wipnote workflow combining session tracking, orchestration, and parallel coordination. |
This skill is archived. Use
/wipnote:wipnotefor current workflow patterns.
# Session start
wipnote status
wipnote analytics summary
# Create and track work
wipnote feature create "Title"
wipnote feature start <feat-id>
# Mark complete
wipnote feature complete <feat-id>
# Features
wipnote feature create "Title"
wipnote feature start <feat-id>
wipnote feature complete <feat-id>
wipnote find features --status todo
wipnote find features --status in-progress
# Bugs
wipnote bug create "Title" --track <trk-id>
wipnote bug start <bug-id>
wipnote bug complete <bug-id>
# Spikes (investigation)
wipnote spike create "Title"
wipnote spike start <spike-id>
wipnote spike complete <spike-id>
# Tracks (multi-feature initiatives)
wipnote track new "Title"
wipnote analytics summary
wipnote analytics summary
wipnote snapshot --summary
wipnote find features --status todo
Dispatch independent tasks in a single message:
# All in one message = parallel execution
Task(subagent_type="wipnote:gemini-operator", prompt="Research...")
Task(subagent_type="wipnote:sonnet-coder", prompt="Implement feat-123...")
Task(subagent_type="wipnote:sonnet-coder", prompt="Implement feat-456...")
See /wipnote:orchestrator-directives-skill for complete patterns.
Work type is inferred from work item ID prefix:
feat-* → feature-implementationspike-* → spike-investigationbug-* → bug-fixchore-* → maintenancewipnote 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.