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

guide/skills-integration.md

View on GitHub
# DeepWorkPlan Guide — Skills & Agents Integration

> Part of the DeepWorkPlan methodology guide. The routing index is
> [`GUIDE.md`](GUIDE.md); read only the guide files your flow names.

## 11. Skills & Agents Integration (MANDATORY)

When creating deep work plans, the plan generator **MUST** consult the project's available Skills and Agents to produce higher-quality, more consistent plans.

### Why This Matters

- Skills contain battle-tested, step-by-step procedures for common tasks
- Agents provide specialized validation checklists and review expertise
- Skills now have **`model` routing** (haiku/sonnet/opus) for cost-efficient execution
- Skills have **`allowed-tools`** restrictions for safer execution
- Agents have **`tools`/`permissionMode`** for controlled access
- Using skill invocation (`/skill-name`) leverages these features automatically

### Where to Find Skills & Agents

Before creating any plan, the generator **MUST** read:

1. **Skills catalog:** `.agents/docs/skills_agents_catalog.md`
   - Lists all available skills with names, tiers, models, file paths, and descriptions
2. **Individual skill files:** `.agents/skills/{skill-name}/SKILL.md`
   - Contains detailed step-by-step procedures, guardrails, and validation
   - Frontmatter includes `model`, `allowed-tools`, and other routing metadata
3. **Agent files:** `.agents/agents/{agent-name}.md`
   - Contains specialized checklists, workflows, and validation criteria
   - Frontmatter includes `tools`, `model`, and `permissionMode`

> `.claude/` and `.cursor/` are symlinks to `.agents/` — all three paths work.

### How to Integrate Skills into Task Files

When writing a task file (`N.task_*.md`), the plan generator **MUST**:

1. **Check if a relevant skill exists** for the task's objective
   - Example: Task is "Update project documentation" → use `/doc-update` skill
   - Example: Task is "Summarize research findings" → use `/research-summary` skill
   - Example: Task is "Create a cross-project plan" → use `/multi-project-plan` skill

2. **If a matching skill exists, instruct invocation in the task instructions:**

   ```markdown
   ## 1. Context

   **Complexity:** Tier {N} ({Light|Standard|Heavy})
   **Primary Skill:** `/{skill-name}` (model: {haiku|sonnet|opus})

   ## 3. Instructions

   **Invoke the skill:** `/{skill-name}`

   This skill will:
   - Use the model configured in its frontmatter (e.g., `model: sonnet`)
   - Restrict tools to only what it needs (e.g., `allowed-tools: Read, Write, Edit, Glob, Grep`)
   - Follow its built-in procedure automatically

   **Additional context for this specific task:**
   - [task-specific additions or overrides]
   - [plan-specific constraints]
   ```

3. **If no matching skill exists**, write instructions normally (as before)

4. **For validation steps, delegate to agents:**
   - Example: Task involves documentation → delegate to `doc-writer` agent
   - Example: Task involves research analysis → delegate to `researcher` agent
   - Example: Task involves multi-project coordination → delegate to `planner` agent

   ```markdown
   ## 5. Validation

   Standard validations:
   - [project-specific commands]

   Agent-based validation (delegated):
   - Delegate to `{agent-name}` agent for {specific concern}
     - The agent will use its configured `tools` (e.g., read-only) and `model`
     - It will follow its built-in checklist and report findings
   ```

5. **Always prefer skill invocation over ad-hoc instructions** when a skill covers
   the task's objective, even partially. The skill has been tested and refined;
   ad-hoc instructions have not.

### How to Reference Skills & Agents in Plan README

The plan's `README.md` should include a section listing which skills and agents are relevant, **including the model column** for execution cost visibility:

```markdown
## Skills & Agents Used in This Plan

| Task | Skill/Agent | Model | Purpose |
|------|-------------|-------|---------|
| Task 1 | `/doc-update` skill | haiku | Documentation update procedure |
| Task 3 | `/research-summary` skill | sonnet | Research summarization |
| Task 5 | `doc-writer` agent | sonnet | Documentation quality validation |
| Task 8 | `planner` agent | opus | Multi-project coordination review |
```

This gives the executor (and the user) visibility into:
- Which tasks will be fast/cheap (haiku) vs. expensive (opus)
- Total model usage across the plan
- Where optimization is possible

If no skills or agents are relevant to the plan, include the section with a note:

```markdown
## Skills & Agents Used in This Plan

No existing skills or agents are directly applicable to this plan's tasks.
Consider creating new skills if patterns emerge during execution.
```

### Execution Checklist Updates

Task files should reference skill invocation in their execution checklists:

```markdown
* [ ] 1. Read this task file fully and understand the goal and constraints
* [ ] 2. Invoke `/{skill-name}` skill (auto-routes to correct model and tools)
* [ ] 3. Apply task-specific additions listed in Instructions section
* [ ] 4. Run standard validations
* [ ] 5. Delegate to `{agent-name}` agent for quality check (if applicable)
* [ ] 6. Commit changes with conventional format
```

### Task-Local Skills Decisions (Output Direction)

Every task decides, **as it completes and while its evidence is in context**, whether its work produced:
- New patterns created → potential new skills/agents
- Changes to existing patterns → potential updates to existing skills/agents
- Skills generator system improvements needed

The disposition (`none` / `update` / `create` / `defer`) is recorded in the task's Completion & Log; real candidates go to `analysis_results/SKILLS_CANDIDATES.md` by stable ID, and warranted in-scope authoring happens inside that task before its gate (`execution.md` §6.1). The Final Review reconciles the ledger — it does not rediscover the plan.

This complements the existing input direction (using existing skills in plans).
The full cycle: Catalog → Plan (input) → Execution (task-local decisions) → Final Review (reconciliation) → Catalog (output)

### Keeping the Registry Updated

**CRITICAL:** The skills/agents catalog **MUST** be kept up to date.

- When a plan creates new skills or agents, update the catalog immediately
- When a skill or agent is deprecated, remove it from the catalog
- The catalog (`.agents/docs/skills_agents_catalog.md`) is the **SINGLE SOURCE OF TRUTH** for what's available
- Also update `.agents/README.md`'s quick reference tables when the catalog changes
- If the catalog is outdated, plans will reference non-existent procedures or miss available ones

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