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

examples/PROMPTS_TEMPLATE.md

View on GitHub
# Ready-to-Use Prompts for {PLAN_NAME}

This file contains **copy-paste ready prompts** for working with this specific plan.

**Plan location:** `.dwp/plans/{PLAN_NAME}/`

---

## 📝 Instructions for Agents Creating This File

**When generating PROMPTS.md for a new plan:**

1. **Use this template** as the base structure
2. **Replace all instances of `{PLAN_NAME}`** with the actual allocated plan
   basename (e.g., `PLAN_001_document_domain_app`). For an existing unnumbered
   plan, use its unchanged basename.
3. **Reference the canonical examples** in the skill's `examples/` folder and the
   command sub-skills:
   - See `examples/CREATE_PLAN.md` for create prompt patterns
   - See the **Execute** sub-skill (`execute/SKILL.md`) for execution behavior
   - See the **Resume** sub-skill (`resume/SKILL.md`) for resume behavior
4. **Customize if needed** based on plan-specific requirements (validations, commit formats, etc.)
5. **Keep prompts simple** - use the simple format from examples unless detailed is needed

**This ensures consistency with the canonical examples while providing plan-specific ready-to-use prompts.**

---

## 🚀 Execute This Plan

**Use this to start executing the plan from the beginning:**

```
Execute the plan at: .dwp/plans/{PLAN_NAME}/README.md

Work on tasks in order. Run validations. Commit after each task.
```

**With specific requirements:**

```
Execute the plan at: .dwp/plans/{PLAN_NAME}/README.md

Important for this plan:
- [Add any plan-specific validations or requirements]

Work on tasks in order. Run validations. Commit after each task.
```

---

## ⏯️ Resume This Plan (After Interruption)

**Use this when execution was interrupted (internet loss, IDE crash, break, etc.):**

```
RESUME the plan at: .dwp/plans/{PLAN_NAME}/README.md

Check task list. Continue from first [ ] task. Review git log.
```

---

## 📊 Resume With Status Report

**Use this when you want to know exactly what's done before resuming:**

```
RESUME the plan at: .dwp/plans/{PLAN_NAME}/README.md

Before resuming, report:
1. Which tasks are [x] vs [ ]?
2. What does git log show? (last 10 commits)
3. Any uncommitted changes? (git status)
4. What's in the current task's log?

Then continue from first [ ] task.
```

---

## 📋 Check Plan Status (Without Executing)

**Use this to check progress without continuing execution:**

```
Check status of: .dwp/plans/{PLAN_NAME}/README.md

Report:
1. Which tasks are [x] vs [ ] in the plan README?
2. What does git log --oneline -10 show?
3. What does git status show?
4. What's in the last task's Completion & Log section?

Tell me where we are in the plan.
```

---

## 🔧 Modify This Plan

**Use this when you need to add/remove/reorder tasks mid-execution:**

```
PAUSE execution of: .dwp/plans/{PLAN_NAME}/README.md

I need to modify the plan:
[Describe what you want to change]

After I manually update the plan files, I'll ask you to resume.
```

---

## 💡 Quick Actions

| Action                      | Prompt to Use             |
| --------------------------- | ------------------------- |
| Start execution             | Execute This Plan         |
| Continue after interruption | Resume This Plan          |
| Need status first           | Resume With Status Report |
| Just check progress         | Check Plan Status         |
| Change plan structure       | Modify This Plan          |

---

## 📚 Related Documentation

When creating or customizing these prompts, reference:

- **[CREATE_PLAN.md](./CREATE_PLAN.md)** - Canonical examples for creating plans
- **Execute** sub-skill (`../execute/SKILL.md`) - Execution behavior
- **Resume** sub-skill (`../resume/SKILL.md`) - Resume behavior
- **Status** sub-skill (`../status/SKILL.md`) - Status reporting
- **[../guide/GUIDE.md](../guide/GUIDE.md)** - Methodology guide routing index (read the file your flow needs)

---

**Note:** These prompts are pre-configured for this specific plan. Just copy and paste to your agent!

**For agents:** When generating this file, use the examples in the skill's `examples/` folder as reference to ensure consistency and best practices.
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