القائمة
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 المهني
Create blog posts — from a topic (writes content) or with provided content (scaffolding). Use proactively when creating new blog posts or articles.
Pre-publication audit for blog posts — comprehensive final review of SEO, AEO, accessibility, images, content quality, i18n parity, and project conventions before publishing. Use proactively before publishing any blog post.
Pre-publication audit for blog series — validates series definition, post ordering, cross-post consistency, navigation, and runs individual post audits for all posts in the series. Use proactively before publishing any blog series.
Audit the blog tag taxonomy — frequency analysis, orphan detection, hierarchy validation, and proposals for new subtopic tags. Read-only — proposes, never modifies tags or posts. Use proactively before each release cycle or after a content drop of 5+ posts.
Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill (DailybotHQ/agent-skill) and/or the Dailybot CLI (DailybotHQ/cli), wiring the plan lifecycle into best-effort agent updates - kickoff when a plan starts, significant task completions, a blocked report when an unattended run halts, and a milestone on plan completion - with payloads derived from the plan's state layer, and optionally committing the Dailybot skill's deterministic hook enforcement (dailybot hook lifecycle hooks, CLI >= 1.12.0) so the agent harness itself reminds agents about unreported work. 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.
| 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.15.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.