AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Deepworkplan Status

skill-dailybothq-deepworkplan-skill-status · by DailybotHQ

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.

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-dailybothq-deepworkplan-skill-status

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-dailybothq-deepworkplan-skill-status)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Deepworkplan Status? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

DeepWorkPlan — Status

Report the current state of one or more Deep Work Plans — progress, completed tasks, current task, blockers — without executing or modifying anything.

Shared resources (read these)

  • [../shared/context.sh](../shared/context.sh) — resolve dwp_dir.
  • [../shared/dwp-paths.md](../shared/dwp-paths.md) — plans at

.dwp/plans/PLAN_{name}/.

Parameter Support

  • /dwp-status {plan_name} — check a specific plan.
  • /dwp-status latest — check the most recently modified plan.
  • /dwp-status all — check all plans.
  • No parameter → interactive scope selection (Step 1).

Normalize the PLAN_ prefix; validate that single plans exist under .dwp/plans/. If not found, show available plans and ask the user to choose.

Workflow

Step 0 — Check for Parameters

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.

Step 1 — Ask for Scope

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.

Step 2 — Gather Status Information

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 %.

Step 3 — Generate Status Report

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.

Step 4 — Additional Information (optional)

Offer deeper detail for any plan: all task files and status, git diff for uncommitted changes, full last-task completion log, any blockers.

Step 5 — Quick Actions

Suggest: resume (/dwp-resume PLAN_{name}), execute (/dwp-execute PLAN_{name}), or open a specific task file.

Status Classifications

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).

Important Notes

  • Read-only: never executes or modifies plans; git status is reported, not

committed. Cross-reference the README task list with git commits for accuracy.

Error Handling

  • Plan folder doesn't exist → report; list available plans; ask to select.
  • README missing → report incomplete structure; list what exists; suggest

/dwp-create.

  • No plans exist → report "No plans found in .dwp/plans/"; suggest

/dwp-create.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.