work-packages
When asked to create a work package (aka WP), or are using a skill that depends on work packages, or are given a work package to complete, use this skill to understand the correct methodology.
When & Why to Use This Skill
This Claude skill provides a robust framework for managing complex tasks through 'Work Packages' (WP). It streamlines the project lifecycle by offering standardized templates for both master and scoped tasks, ensuring that goals, hypotheses, and results are systematically tracked and persisted across agent sessions. By implementing a defined lifecycle from draft to completion, it enhances the agent's ability to maintain context and deliver measurable outcomes in long-term projects.
Use Cases
- Project State Persistence: Maintaining continuity in long-running or multi-session projects by documenting the current state, goals, and results in a structured format that survives session resets.
- Hypothesis-Driven Problem Solving: Utilizing the Master WP template to define clear hypotheses and validation metrics before executing technical changes, ensuring every action is data-driven and evaluable.
- Task Scoping and Delegation: Breaking down large-scale objectives into manageable 'Scoped Work Packages' with clearly defined boundaries, specific approaches, and explicit success criteria to prevent scope creep.
- Iterative Result Tracking: Recording multiple iterations of results and evaluations within a single document to provide a transparent audit trail of the project's evolution and learning process.
| name | work-packages |
|---|---|
| description | When creating or working on a work package (WP), load this skill to get templates and understand the WP lifecycle. |
Work packages persist project/task state between agent sessions.
Work packages can either by for the entire project (#master-work-package-template), or a scoped task (#scoped-work-package-template).
Work Package Lifecycle
- create in .opencode/work/drafts/wp-{name}.md
- move to /in-progress when starting
- record results
- iterate until
- move to /completed when done
Master Work Package Template
# {Title}
## Goal
{What needs to be solved}
## Hypothesis
{Why you think this will work (or not work)}
## Validation
{How you will measure and test the results}
## Results
To be filled out upon completion. Can contain multiple iterations.
## Evaluation
What did your learn from the results? Was the hypothesis proved correct?
Scoped Work Package Template
# {Title}
## Goal
{What needs to be solved}
## Scope
{What is in or out of scope; what will be affected}
## Hypothesis
{Why you think this will work (or not work)}
## Approach
{How you intend to achieve the goal}
## Validation
{How you will measure and test the results}
## Results
To be filled out upon completion. Can contain multiple iterations.
## Evaluation
What did your learn from the results? Was the hypothesis proved correct?