semi-autonomous-developer

Automated story implementation creates a feature branch, executes an incremental task plan, verifies compilation and tests, commits changes, and prepares a pull request. It manages sprint backlog states including STARTED and BLOCKED for professional, incremental delivery on small, well-scoped tasks.

Semi-autonomous story development automates the implementation of sprint-backed user stories by incrementally planning tasks, writing tests, committing code, and updating the sprint backlog. It reduces manual coordination for small, well-scoped software development tasks.

Create a feature branch named feature/summary-of-story-title, implement the story incrementally with tests, then mark the story as BLOCKED awaiting review. Push the branch to create a pull request, ensuring the sprint backlog reflects STARTED and BLOCKED states accurately.

Yes, this workflow applies to sprint-backed software projects requiring incremental delivery and rigorous testing across small, well-scoped tasks. It satisfies requirements to manage an incremental task plan, verify compilation, and update the sprint backlog.

The workflow locates the current sprint backlog in doc/agile/v0/ by matching the pattern sprint_backlog_*.org. This structured backlog format is required to manage incremental task plans and track STARTED and BLOCKED statuses.

Avoid using this workflow for large, poorly scoped tasks or projects lacking a structured sprint backlog. It requires small, well-scoped tasks and a sprint backlog file to manage incremental delivery, verify compilation, and update BLOCKED status correctly.