equinoxe-grammer/minimalist-agile-engineering
Minimalist agile engineering workflows for small, verifiable software increments.
Use when a request changes contracts, boundaries, persistence, security, deployment, or multiple independent subsystems and needs a reviewed design before implementation.
Use when a manual workflow is a candidate for automation and its repetition, stability, value, maintenance cost, and failure handling need evaluation.
Use when a product backlog contains duplicate, oversized, weakly valuable, stale, or unordered stories before selecting a sprint.
Use when a software request is ambiguous, solution-led, over-scoped, or missing a measurable outcome, user, constraint, or explicit non-goal.
Use when software work needs minimal scope, incremental delivery, explicit evidence, Scrum-style iteration, or protection against premature automation and silent scope expansion.
Use when a small, local, low-risk change has clear acceptance and does not need a full backlog, sprint, or architectural design.
Use when a software request must be routed through a fast change, feature prototype, architectural design, sprint cycle, review, or next-iteration workflow.
Use when an approved outcome needs bounded requirements, acceptance criteria, explicit exclusions, risks, dependencies, or a smallest valuable increment before story creation.
Use when implementing a selected sprint increment and the agent must preserve story scope, test behavior, record evidence, and keep unselected backlog work out of the change.
Use when selected user stories need an executable implementation plan with tasks, tests, dependencies, risks, a timebox, and a Definition of Done.
Use when a sprint review is complete and the team must preserve learning, remove waste, adapt the backlog, and define concrete actions for the next iteration.
Use when a sprint increment is ready to demonstrate and each selected story needs an acceptance decision, user feedback, and a traceable follow-up.
Use when an ordered backlog must be reduced to a bounded prototype or sprint with one goal, explicit exclusions, capacity, and a demonstrable increment.
Use when a bounded specification must be decomposed into independent user stories with value, acceptance criteria, dependencies, and traceable history.