gds-dev-story

Invoke the dev story workflow and it reads sprint-status.yaml to find the first story marked ready-for-dev, loads its full spec, and implements every task in order. You can also pass an explicit story file path to develop a specific story.

Each task follows a red-green-refactor cycle: failing tests are written first, then minimal code makes them pass, then the code is refactored while keeping tests green. A task is only marked complete when all tests exist and pass with no regressions.

Yes. It detects a Senior Developer Review section in the story file, counts unchecked review follow-up items, and prioritizes resolving those findings before continuing with regular tasks, marking both the task and the review action item as resolved.

The workflow reports that no ready stories were found and offers options: run create-story to draft a new story, run validate-create-story for a quality check, provide a specific story file path, or review the current sprint status.

It halts when the story file is inaccessible, requirements are ambiguous, new dependencies beyond the spec are needed, three consecutive implementation failures occur, required configuration is missing, or definition-of-done validation fails.