メニュー
Report the status of a Deep Work Plan — completed tasks, what's left, and blockers — without executing. Use when the developer asks for plan status or what remains.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill and/or the Dailybot CLI, and wiring a best-effort progress/milestone report into DWP execution so a plan completion surfaces to the team. Opt-in, never required, never blocks the work, reconciles existing setups instead of clobbering them, and defers all auth to the Dailybot skill's own consent flow. Use when the developer or team already uses Dailybot and wants DWP progress visible to humans.
Optional DeepWorkPlan addon that safely upgrades a repo's dependencies — reasoning about the repo's ACTUAL package manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer, and more) rather than assuming npm — with a batched, validated, revertible workflow that detects the manager and manifests/lockfiles, classifies upgrades (patch/minor/major), upgrades in safe batches, runs the repo's real validation gate after each batch, reverts a failing batch, and summarizes. Opt-in, never required, reconciles with the repo's existing tooling. Use when the developer wants to bring dependencies up to date without breaking the build.
Optional DeepWorkPlan addon that gives a frontend/UI repo a DESIGN.md (under docs/, indexed from AGENTS.md) — a Markdown design-system file any coding agent reads to generate UI consistent with the repo's OWN design system. Reasons about the repo's ACTUAL design tokens (CSS custom properties, Tailwind config, token files, component styles) rather than copying a brand file; documents colors & roles, typography, spacing/layout, elevation, shapes, components, responsive behavior, do's & don'ts, and an agent prompt guide; checks contrast (WCAG AA) and token integrity. Frontend-scoped and default-on when a UI/design system is detected (applied in trust mode, strongly recommended in guided mode; never offered for backend/CLI/library-only repos); never required for baseline conformance; reconciles an existing DESIGN.md instead of clobbering it. Use when the developer wants agents to produce on-brand, consistent UI for a frontend repo.
Optional DeepWorkPlan addon that adds (or reconciles) a compose-based devcontainer to a repo — base image and supporting services reasoned from the detected stack, with persistent AI-CLI auth, the dailybot-project-network, the DOCKER_DEV_ENV=vscode convention, and project-identity precedence. Opt-in, never required, reconciles existing setups instead of clobbering them. Use when the developer wants a reproducible isolated dev container for an AI-first repo.
Author or update reusable skills, agents, and commands in the current repo — reason about the repo's .agents/ layout, follow the Open Agent Skills frontmatter contract, and keep the .agents/docs/ catalog in sync. Use when a developer wants to create or evolve the repo's agent kit (skills, agents, commands), or runs /skill-create or /agent-create.
Create a Deep Work Plan. Gather context, draft, and refine into a single final plan under .dwp/plans/, with a refined draft staged in .dwp/drafts/. Use when the developer wants a new structured multi-task plan.
| name | deepworkplan-status |
| description | Report the status of a Deep Work Plan — completed tasks, what's left, and blockers — without executing. Use when the developer asks for plan status or what remains. |
| version | 2.7.0 |
| documentation_url | https://deepworkplan.com |
| user-invocable | true |
| allowed-tools | Bash, Read, Grep, Glob, Edit, Write |
Report the current state of one or more Deep Work Plans — progress, completed tasks, current task, blockers — without executing or modifying anything.
../shared/context.sh — resolve dwp_dir.../shared/dwp-paths.md — plans at
.dwp/plans/PLAN_{name}/./dwp-status {plan_name} — check a specific plan./dwp-status latest — check the most recently modified plan./dwp-status all — check all plans.Normalize the PLAN_ prefix; validate that single plans exist under
.dwp/plans/. If not found, show available plans and ask the user to choose.
all → scope "all", skip to Step 2. latest → most recent plan, scope "single",
skip to Step 2. Otherwise normalize the name, validate, scope "single", skip to
Step 2. No parameter → Step 1.
List PLAN_* folders in .dwp/plans/; mark the most recently modified as
latest. Offer: a single plan (from a numbered list), all plans, or latest.
Accept a number, name, all, or latest.
For each plan: read the README (goal, task list [x]/[ ], plan-status notes);
run git status and git log --oneline -20; read the last completed task's
Completion & Log and the current [ ] task file; compute totals and progress %.
Single plan: header with Plan Status: PLAN_{name} and location
.dwp/plans/PLAN_{name}/; goal; progress (total / completed / pending / %);
completed tasks; pending tasks; current status (last completed, next task,
uncommitted work, recent commits); notes from the README; last task log summary.
All plans: a one-line-per-plan summary (progress, status, last activity), then the single-plan detail block for each.
Offer deeper detail for any plan: all task files and status, git diff for
uncommitted changes, full last-task completion log, any blockers.
Suggest: resume (/dwp-resume PLAN_{name}), execute (/dwp-execute PLAN_{name}),
or open a specific task file.
Not started (all [ ], no commits) · In progress (mixed, recent activity) ·
Complete (all [x]) · Blocked (current task has a blocker note) · Stale (no
activity for a long time — optional).
git status is reported, not
committed. Cross-reference the README task list with git commits for accuracy./dwp-create..dwp/plans/"; suggest
/dwp-create.