akoita/utilities

Create, reorganize, or maintain useful software-project documentation. Use when scaffolding documentation for a new repository, normalizing an existing docs tree, writing architecture or design documentation, or updating docs after a change that materially alters behavior, interfaces, architecture, operations, configuration, or security. Scale the result to the project's maturity and risk; do not use for unrelated prose or exhaustive code narration.

Plan an executable project milestone by discovering repository guidance, roadmap and planning context, milestone history, open issues, and dependency relationships; balance candidates across business value, usability, known issues, and new needs, then propose a goal-shaped milestone. Use when a user asks to plan a milestone or sprint across multiple issues. Keep tracker writes behind explicit approval; do not use for starting or finishing one issue.