Skip to content

j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan

deepworkplan

Verified

DeepWorkPlan — turn any repo AI-first and run Deep Work Plans. Routes to create, execute, refine, resume, status, verify, upgrade, and repo-onboarding sub-skills based on intent. Use when the developer wants to plan, execute, manage, or verify structured multi-task work, or make a repository AI-agent-ready.

FileKindSize
SKILL.mdskill md12.0 KB
TRUST.mdmarkdown16.1 KB
addons/README.mdmarkdown11.7 KB
addons/machine-installs.mdmarkdown2.9 KB
examples/CREATE_PLAN.mdmarkdown6.9 KB
examples/ORCHESTRATOR_TASK_TEMPLATE_create_child_dwp.mdmarkdown15.0 KB
examples/ORCHESTRATOR_TASK_TEMPLATE_execute_child_dwp.mdmarkdown16.7 KB
examples/ORCHESTRATOR_TASK_TEMPLATE_integration_checkpoint.mdmarkdown9.0 KB
examples/PROMPTS_TEMPLATE.mdmarkdown4.0 KB
examples/TEAM_AGENTS_TASK_TEMPLATE.mdmarkdown5.1 KB
examples/V6_PLAN_EXAMPLE.mdmarkdown5.5 KB
guide/GUIDE.mdmarkdown8.0 KB
guide/authoring.mdmarkdown28.5 KB
guide/execution.mdmarkdown21.0 KB
guide/large-repo-onboarding.mdmarkdown3.3 KB
guide/orchestration-at-scale.mdmarkdown11.4 KB
guide/orchestrator.mdmarkdown37.9 KB
guide/prompts.mdmarkdown10.1 KB
guide/skills-integration.mdmarkdown6.5 KB
guide/structure.mdmarkdown6.2 KB
guide/swarm.mdmarkdown21.2 KB
guide/team-agents.mdmarkdown12.3 KB
shared/adaptation.mdmarkdown2.7 KB
shared/addon_sync.pyscript17.7 KB
shared/benchmark.pyscript97.6 KB
shared/config.pyscript41.5 KB
shared/context.shscript4.2 KB
shared/context_manifest.pyscript40.8 KB
shared/contract_v6.pyscript82.7 KB
shared/delegators.pyscript3.0 KB
shared/dwp-paths.mdmarkdown5.8 KB
shared/finalize_plan.pyscript7.2 KB
shared/install-verification.mdmarkdown1.8 KB
shared/ledger.pyscript141.5 KB
shared/migrate_v6.pyscript46.5 KB
shared/outcomes.pyscript27.2 KB
shared/plan_paths.pyscript4.8 KB
shared/resources.pyscript49.0 KB
shared/scheduler.pyscript41.6 KB
shared/state_contract.pyscript9.8 KB
shared/swarm.pyscript27.3 KB
shared/troubleshooting.mdmarkdown7.4 KB
shared/update-state.pyscript12.5 KB
shared/views.pyscript21.0 KB
shared/working-principles.mdmarkdown7.1 KB
spec/ADDONS.mdmarkdown27.4 KB
spec/AGENT_PROTOCOL.mdmarkdown28.0 KB
spec/ARCHETYPES.mdmarkdown10.6 KB
spec/BENCHMARK.mdmarkdown20.3 KB
spec/CONFIG.mdmarkdown8.7 KB
spec/DOCUMENTATION_STANDARD.mdmarkdown40.7 KB
spec/DWP_SPECIFICATION.mdmarkdown65.1 KB
spec/LITE_PLANS.mdmarkdown4.0 KB
spec/PLAN_STATE.mdmarkdown34.9 KB
spec/README.mdmarkdown11.5 KB
spec/V6_CONTEXT.mdmarkdown6.4 KB
spec/V6_CONTRACT.mdmarkdown12.3 KB
spec/V6_LIFECYCLE.mdmarkdown13.5 KB
spec/V6_RESOURCES.mdmarkdown4.7 KB
spec/V7_ABILITIES.mdmarkdown4.9 KB
spec/V7_CONTRACT.mdmarkdown6.4 KB
spec/V7_ROADMAP.mdmarkdown4.6 KB
spec/schema/addon-descriptor-v1.schema.jsonconfig5.5 KB
spec/schema/benchmark-record.schema.jsonconfig14.0 KB
spec/schema/context-manifest-v6.schema.jsonconfig12.5 KB
spec/schema/dwp-config-v1.schema.jsonconfig3.5 KB
spec/schema/dwp-handoff-v1.schema.jsonconfig3.0 KB
spec/schema/journal-event-v6.schema.jsonconfig22.3 KB
spec/schema/journal-event-v7.schema.jsonconfig24.9 KB
spec/schema/learnings-record.schema.jsonconfig6.0 KB
spec/schema/plan-contract-v6.schema.jsonconfig16.4 KB
spec/schema/plan-contract-v7.schema.jsonconfig16.6 KB
spec/schema/plan-manifest-v2.schema.jsonconfig1.0 KB
spec/schema/plan-manifest-v5.schema.jsonconfig1.3 KB
spec/schema/plan-manifest-v6.schema.jsonconfig2.0 KB
spec/schema/plan-manifest-v7.schema.jsonconfig1.7 KB
spec/schema/plan-manifest.schema.jsonconfig1.8 KB
spec/schema/plan-snapshot-v6.schema.jsonconfig7.8 KB
spec/schema/plan-state-v2.schema.jsonconfig6.4 KB
spec/schema/plan-state-v5.schema.jsonconfig6.7 KB
spec/schema/plan-state.schema.jsonconfig3.7 KB

shared/dwp-paths.md

View on GitHub
# dwp-paths.md — The `.dwp/` Output Convention

> Source of truth for **where Deep Work Plan outputs live**. Every DeepWorkPlan
> sub-skill reads this to resolve plan paths.

## The convention

All plans live under a single gitignored repo-root directory, `.dwp/`:

```
.dwp/
└── plans/      ← PLAN_001_{name}/, PLAN_002_{name}/, ... (flat)
```

- New plans live at `.dwp/plans/PLAN_<id>_<name>/`, Lite or Full alike.
  `id` is an incrementing decimal number with at least three digits, allocated
  by `plan_paths.py`. Old `PLAN_{name}/` folders remain valid and stay in place.
  At 1000 the ID expands to four digits; `list` still sorts it numerically.
  Never renumber or move an existing plan: its basename is referenced by
  manifests, contracts, journals, prompts and evidence.
- To select a plan, use `python3 ../shared/plan_paths.py --plans-dir
  <dwp_dir>/plans resolve <selector>`. A selector can be the full folder name,
  its numeric ID (`1` or `001`), a unique slug, or `latest`. `latest` means the
  highest allocated ID when numbered plans exist; otherwise it uses the most
  recently modified legacy folder. Ambiguous slugs require the full name or ID.
  `list` shows numbered plans in numeric order and then legacy plans.
- The allocator keeps `.next-plan-id` in `plans/`, so deleting an old plan does
  not reuse its number. A crash may leave a gap or an empty folder; neither
  silently changes the identity of another plan.
- `create` writes the plan folder directly. There is no separate draft artifact
  and no `.dwp/drafts/` directory: the Lite plan **is** the reviewable artifact
  (`../spec/LITE_PLANS.md`). Both were removed in 2.4.0. A `.dwp/drafts/` folder
  left over from an earlier version is inert — DWP neither reads nor writes it.
- Every artifact a plan produces — analysis outputs, gate logs, generated
  reports — lives inside **that plan's own folder**, under
  `.dwp/plans/<plan>/analysis_results/`. Temporary or analysis results
  **MUST NOT** be written to the repository root or to ad-hoc folders elsewhere
  in the repo: the plan folder is the single home for a plan's working
  artifacts, so a plan can be inspected, archived, or deleted as one unit.

## Default location & override

- **Default:** `<repo-root>/.dwp/`, where `<repo-root>` is the git toplevel (or
  the current directory outside a git work tree). `shared/context.sh` resolves
  this and emits it as the `dwp_dir` field.
- **Override:** set the `DWP_DIR` environment variable to an absolute path to
  relocate the output directory (e.g. for monorepos that keep outputs elsewhere,
  or CI sandboxes). `context.sh` honors `DWP_DIR` when present.

## `.dwp/` is gitignored

`.dwp/` **MUST** be ignored by the repository's `.gitignore`. Plans are
working artifacts, not tracked source. The one tracked file it may hold is
the addon registry `.dwp/config.json` (`../spec/CONFIG.md` §1): the rule
`.dwp/*` + `!.dwp/config.json` keeps everything else ignored (a plain
`.dwp/` rule keeps the registry local). (Orchestrator hubs follow the same rule:
child plans live at `repositories/{repo}/.dwp/plans/<plan>/`, also
gitignored; numbering is local to each managed repository.)

## Workspace persistence and transfer

Because `.dwp/` is gitignored, **a fresh `git clone` carries no plan data**.
That is by design — plans are working state, not source — and it has one
consequence a resuming agent MUST state plainly: a checkout without `.dwp/`
has nothing to resume, and progress is never fabricated from commits alone.

**Same workspace.** The plan folder on disk is the whole recovery surface;
`resume/SKILL.md` Step 2 (assess, reconcile, classify the interruption
boundary) needs nothing else.

**Transfer to a new machine (explicit, manual).** The minimum handoff
manifest — everything a resumed session needs, nothing it can reconstruct:

1. **The complete plan folder** `.dwp/plans/<plan>/`: README, task
   files, `PROGRESS.md`, `manifest.json`, `state.json`, and
   `analysis_results/` **including every gate log cited by a `log=` evidence
   pointer** (a dangling pointer is a conformance finding, not reusable
   evidence).
2. **Repository revision(s)** the state cites — `git rev-parse HEAD` per
   repository, checked out on arrival.
3. **Required dirty work**: any uncommitted changes the checkpoint names,
   re-created or carried over (patch, stash bundle, or copy).
4. **Evidence pointers** to external-action receipts (report ids, PR URLs)
   recorded in the task logs — the receipts themselves live in their
   services and are investigated there when absent.

If the destination will create further plans in the same sequence, also carry
`.dwp/plans/.next-plan-id`. Transferring a single plan folder is enough to
resume that plan; the counter preserves IDs of plans deleted before transfer.

On arrival: restore the folder at the same relative path, check out the
recorded revision, re-create the dirty work, then run the read-only checker
(`verify/plan_contract.py`) before resuming. **Missing-artifact behavior:**
report what is missing and stop at that boundary — never reconstruct history
from memory or guess at absent evidence.

**No infrastructure.** There is no daemon, no auto-upload, and no automatic
unignoring of `.dwp/`, and none may be implied: preservation is a deliberate
copy (archive the plan folder, or move it with the workspace) performed by a
human or an agent acting on explicit instruction.

## Contrast with the legacy path

`.dwp/` **replaces** the legacy DWP output tree:

| Concept | Legacy path | New path |
|---------|-------------|----------|
| Plans | `.agent_commands/agent_deep_work_plans/results/plans/PLAN_{name}/` | `.dwp/plans/<plan>/` |

The legacy `.agent_commands/agent_deep_work_plans/results/` tree **MUST NOT** be
used by repos onboarded to DeepWorkPlan v2; migration moves any existing plans
into `.dwp/`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall