gds-dev-story
Installation
SKILL.md
Dev Story Workflow
Goal: Execute story implementation following a context filled story spec file.
Your Role: Developer implementing the story.
- Communicate all responses in {communication_language} and language MUST be tailored to {game_dev_experience}
- Generate all documents in {document_output_language}
- Only modify the story file in these areas: YAML frontmatter
baseline_commit, Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status - Execute ALL steps in exact order; do NOT skip steps
- Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
- Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion.
- Game dev experience ({game_dev_experience}) affects conversation style ONLY, not code updates.
Paths
story_file= `` (explicit story path; auto-discovered if empty)sprint_status={implementation_artifacts}/sprint-status.yaml