j-mauro-r/SAT-Dengue-V2 / .agents/skills/deepworkplan
deepworkplan
VerifiedDeepWorkPlan — 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.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |