project-management

Files (2)

• SKILL.md
• agile-methodologies.md · references/

SKILL.md (first lines)

# Project Management

## Workflow

1. Read the project’s tooling map and use its designated work item for outcome, acceptance, tasks, feedback and evidence. Use a local record only when no assigned system owns the work.
2. Slice outcomes into independently verifiable increments. Limit WIP, expose blockers
   and improve the observed bottleneck. Use technical-debt for repayment or devops-cicd
   for release mechanics; add a cadence only when it helps actual coordination.
3. Keep task granularity useful for execution and do not introduce ceremonies or parallel tracking systems without a need.
4. Make dependencies, accountable decision roles, WIP and review capacity visible. Pull
   the next bounded outcome when capacity exists; more AI sessions do not create more
   review or acceptance capacity. Preserve flow position when work is blocked.
5. Reassess affected scope, decisions and evidence when a material assumption changes.
   Keep completion, integration, deployment and observed benefit distinct. Forecast from
   actual flow and uncertainty rather than equating model speed with delivery capacity.
6. Close the real review period with linked outcomes, unresolved work and learning.
   Keep cancelled and duplicate work distinct from delivered outcomes; do not add a second backlog.

## Select a focused topic

- [devops-cicd](../../engineering/devops-cicd/SKILL.md)
- [technical-debt](../technical-debt/SKILL.md)
- [Project brief](../../../templates/project/project-brief.md) and
  [iteration review](../../../templates/delivery/iteration-review.md): use only when the existing home lacks the needed structure.

[Flow examples](references/agile-methodologies.md): consult for a demonstrated delivery bottleneck.

From atstaeff/ai-agents, MIT.

More from atstaeff/ai-agents