work-management

Files (3)

• SKILL.md
• openai.yaml · agents/
• progress-sync.md · references/

SKILL.md (first lines)

# Work Management

1. Reuse applicable project/process instructions and locate the actual assignment.
   Keep scope, acceptance, dependencies and progress at that shared work home. Record
   collaborative execution steps there when others depend on them or the project requires
   a shared plan. Use the designated plan home when one exists; avoid a second tracker.
   Optional personal steps and experiments stay in the permitted private Second Brain.
   If it is unavailable, label personal planning unsaved and continue authorized work.
   Missing shared access means a proposed unapplied update, not invented synchronization.
2. State outcome, scope, observable acceptance, accountable human, bounded writer scope,
   dependencies and integration owner. Pull a complete increment within review capacity.
   Coordinate shared contracts and overlapping writes before parallel implementation.
3. Preserve required plan approval and feedback for the current revision. Proceed with
   routine reversible choices in scope; resolve consequential conflicts with their owner.
   A proposal does not revoke an accepted decision. Record significant reasons as they arise.
4. Update the same assignment after material progress or a blocker. Lead with outcome,
   evidence, blocker/owner and next action. Preserve human wording; reread/version-check
   before writes. After a timeout, inspect existing effects before retrying.
5. Link checks to criteria and tested revisions. Reassess affected evidence/approval after
   material changes. Distinguish verified, accepted, integrated, deployed and measured
   benefit; cancelled or duplicate work is not delivery. Keep blocked flow position visible.
6. Before pausing, update private resume state and shared result/evidence at their proper
   homes. Preserve source revisions, blockers, pending writes and one next action. On resuming, compare current sources with
   that handoff. Keep accepted reasons and reusable knowledge at their project-owned homes.

Keep private paths, vault links and raw personal plans out of shared artifacts. An
authorized, sanitized plan extract may support required review; record the reviewed
revision and actual feedback at the designated review home. Share the coordination
facts collaborators need without copying private scratch work.

## Load only when needed

- [Plan review](../../../toolkit/PLAN-REVIEW.md): when the project requires approval.
- [Recovery contract](../../../toolkit/CONTEXT-RECOVERY.md): interruption, conflicting or stale state.
- [Local records](../../../toolkit/WORK-RECORDS.md): only for the optional Markdown workbench.
- [Progress examples](references/progress-sync.md): audience-specific reporting.

From atstaeff/ai-agents, MIT.

More from atstaeff/ai-agents