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/ORCHESTRATOR_TASK_TEMPLATE_integration_checkpoint.md

View on GitHub
# Task {N}: Integration Checkpoint — {Description}

> **Template for orchestrator plans.** Fill in known placeholders when generating a real task file. Resolve each child plan basename from the parent registry after the child has been allocated; never construct an ID from the feature or repository name.

## 1. Context

**Plan Type:** Orchestrator — Integration Checkpoint
**Preceding Child DWPs:** {list child DWPs created before this checkpoint}
**Purpose:** Verify that child DWP plans are compatible and integration points are aligned before proceeding.

This task does NOT execute any child DWP plans. It reviews the created child plans to ensure:
- API contracts are consistent across repos
- Data models use compatible field names and types
- Error handling patterns are aligned
- Naming conventions don't conflict

### Orchestrator Context

- **Parent Plan:** {PARENT_PLAN_NAME}
- **Checkpoint position:** After {child DWP creation tasks}, before {next phase}
- **Manifest:** `.dwp/plans/{PARENT_PLAN_NAME}/ORCHESTRATOR_MANIFEST.md` {or "Not used"}
- **Child DWPs to verify:**
  - `repositories/{repo1}/.dwp/plans/{CHILD_PLAN_NAME_1}/`
  - `repositories/{repo2}/.dwp/plans/{CHILD_PLAN_NAME_2}/`

### Output Contract Verification

This checkpoint also verifies that output contracts are properly defined:
- Each child DWP's "Expected Outputs" section is complete
- Downstream child DWPs' "Input Dependencies" match what predecessors declare as outputs
- The manifest's "Output Contracts" section is consistent with child DWP declarations (if manifest exists)

## 2. Read Before Starting

- All preceding child DWP creation task Completion & Logs
- The created child DWP plan READMEs and key task files
- Any design documents or API contracts from direct tasks in this plan

## 3. Goal

Verify that the child DWP plans created in preceding tasks are compatible and will integrate correctly when executed. Flag any inconsistencies for correction before execution begins.

## 4. Instructions

> **Before starting:** Re-read the plan README section 1 (Goal) to ensure this task's work aligns with the overall objective.

### Step 1: Read all child DWP plans

For each child DWP, read:
- README.md — understand goal and task list
- Key task files — especially those involving:
  - API endpoints / URL definitions
  - Data models / schemas
  - API client / service layer definitions
  - Shared constants or configuration

### Step 2: Verify API Contract Alignment

Check that API-producing repos and API-consuming repos agree on:

| Aspect | Producer ({repo1}) | Consumer ({repo2}) | Match? |
|--------|--------------------|--------------------|--------|
| Base URL / path | {e.g., `/api/v1/preferences/`} | {e.g., `/api/v1/preferences/`} | [ ] Yes / [ ] No |
| HTTP methods | {e.g., GET, PUT, PATCH} | {e.g., GET, PUT, PATCH} | [ ] Yes / [ ] No |
| Request body fields | {field list} | {field list} | [ ] Yes / [ ] No |
| Response body fields | {field list} | {field list} | [ ] Yes / [ ] No |
| Authentication | {e.g., JWT Bearer} | {e.g., JWT Bearer} | [ ] Yes / [ ] No |
| Error format | {e.g., `{error: string}`} | {e.g., `{error: string}`} | [ ] Yes / [ ] No |

### Step 3: Verify Data Model Consistency

Check that field names, types, and required/optional status are consistent:

| Field | {repo1} Type | {repo2} Type | Consistent? |
|-------|-------------|-------------|-------------|
| {field1} | {type} | {type} | [ ] Yes / [ ] No |
| {field2} | {type} | {type} | [ ] Yes / [ ] No |

### Step 4: Verify Naming Conventions

Check that references between repos use consistent naming:
- [ ] API endpoint paths match between producer and consumer task files
- [ ] Event/message names are consistent (if applicable)
- [ ] Shared constants or enums use the same values

### Step 5: Check Error Handling Alignment

Verify that:
- [ ] Error response formats are handled correctly by consumers
- [ ] HTTP status codes are expected correctly
- [ ] Timeout handling is consistent
- [ ] Retry logic doesn't conflict

### Step 6: Verify Output Contracts

Check that output declarations match input dependencies across the dependency chain:

| Producer Child DWP | Declared Outputs | Consumer Child DWP | Required Inputs | Match? |
|-------------------|-----------------|-------------------|----------------|--------|
| {CHILD_PLAN_NAME_1} | {outputs listed in "Expected Outputs"} | {CHILD_PLAN_NAME_2} | {inputs listed in "Input Dependencies"} | [ ] Yes / [ ] No |

For each mismatch:
- Identify what's missing or inconsistent
- Determine which child DWP needs to be updated
- Flag as blocking (if outputs are undefined) or advisory (if outputs exist but descriptions differ)

### Step 7: Verify Manifest Consistency (if manifest exists)

If `ORCHESTRATOR_MANIFEST.md` exists, verify:
- [ ] All child DWPs listed in manifest match the actual created child DWPs
- [ ] Dependency graph in manifest matches dependencies declared in child DWP READMEs
- [ ] Output contracts in manifest are consistent with child DWP declarations
- [ ] Shared context in manifest is reflected in child DWP "Orchestrator Context" sections

If any inconsistency found:
- Update the manifest to match the actual child DWP content (child DWPs are the source of truth)
- Log the fix in the checkpoint report

### Step 8: Assess Execution Readiness

For each execution phase/group, verify:
- [ ] All child DWPs in the current phase have defined validation commands
- [ ] Predecessor dependencies are clearly documented
- [ ] Output expectations are set for downstream consumers
- [ ] No circular dependencies exist

**Execution readiness summary:**

| Phase | Child DWPs | Dependencies Met | Ready? |
|-------|-----------|-----------------|--------|
| Phase 1 (no deps) | {repo1} | N/A | [ ] Yes / [ ] No |
| Phase 2 (depends on Phase 1) | {repo2} | Phase 1 outputs defined | [ ] Yes / [ ] No |

### Step 9: Document Findings

Create a checkpoint report with:
- All verified integration points (API, data model, naming, error handling)
- Output contract verification results
- Manifest consistency results (if applicable)
- Execution readiness assessment
- Pass/fail for each check
- Any issues found with recommended fixes
- Overall compatibility assessment

### Step 10: Handle Issues

**If all checks pass:**
- Mark checkpoint as passed
- Continue to next task

**If issues are found:**
- Document each issue clearly
- For each issue, specify:
  - Which child DWP(s) need modification
  - What the fix should be
  - Whether it's blocking (must fix before execution) or advisory (can fix during execution)
- If blocking issues exist: update the affected child DWP task files to fix the inconsistency
- If only advisory issues: note them for the executing agent to address

## 5. Acceptance Criteria

- [ ] All child DWP plans reviewed
- [ ] API contract alignment verified
- [ ] Data model consistency verified
- [ ] Naming conventions verified
- [ ] Error handling alignment verified
- [ ] Checkpoint report documented in Completion & Log
- [ ] Any blocking issues resolved or flagged
- [ ] Output contracts verified between producer and consumer child DWPs
- [ ] Manifest consistency verified (if manifest exists)
- [ ] Execution readiness assessed for each phase
- [ ] Orchestrator README updated with checkpoint status

## 6. Validation

```bash
# Verify all child DWP plans exist
test -f repositories/{repo1}/.dwp/plans/{CHILD_PLAN_NAME_1}/README.md && echo "PASS: {repo1} child DWP exists" || { echo "FAIL" >&2; exit 1; }
test -f repositories/{repo2}/.dwp/plans/{CHILD_PLAN_NAME_2}/README.md && echo "PASS: {repo2} child DWP exists" || { echo "FAIL" >&2; exit 1; }

# No code validation needed — this is a review task
echo "Integration checkpoint is a manual verification task"
```

## 7. Execution Checklist

- [ ] 1. Read this task file fully.
- [ ] 2. Read all child DWP plans (README + key task files).
- [ ] 3. Verify API contract alignment.
- [ ] 4. Verify data model consistency.
- [ ] 5. Verify naming conventions.
- [ ] 6. Check error handling alignment.
- [ ] 7. Verify output contracts (producer outputs vs consumer inputs).
- [ ] 8. Verify manifest consistency (if manifest exists).
- [ ] 9. Assess execution readiness for each phase.
- [ ] 10. Document findings.
- [ ] 11. Handle any issues (fix blocking, note advisory).
- [ ] 12. Update the plan README to mark this task as `[x]`.
- [ ] 13. Update PROGRESS.md with checkpoint results.
- [ ] 14. Commit: `git commit -m "docs(technical): integration checkpoint passed - Task {N} of {PARENT_PLAN_NAME}"`
- [ ] 15. Send Dailybot progress report (non-blocking).
- [ ] 16. Update the Log section below.

## 8. Completion & Log (filled by the agent)

- **Status:** (completed / blocked / failed validation)
- **Timestamp:**
- **Integration Points Verified:** {count}
- **All Checks Passed:** (yes / no — {count} issues found)
- **Blocking Issues:** {list or "None"}
- **Advisory Issues:** {list or "None"}
- **Output contract checks:** {count} pass / {count} fail
- **Manifest consistent:** (yes / no / N/A — no manifest)
- **Execution readiness:** (all phases ready / {phase} not ready)
- **Overall Assessment:** {Compatible / Needs fixes}
- **Notes / follow-ups:**
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