Automate end-to-end developer story implementation from a story spec.
npx skills add https://github.com/MazenMrad/Obsidio --skill gds-dev-story
Please help me install this Agent Skill. Skill: gds-dev-story Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-dev-story Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-dev-story
Automates the end-to-end implementation of a developer story by transforming a context-filled story spec into concrete tasks, artifacts, and validation workflows, reducing manual interpretation and drift.
Provide the path to the ready story file and initiate the Dev Story Workflow to execute implementation.
High-intent search queries and answers about installing and using this skill.
Automating story implementation involves loading a context-filled story spec to orchestrate discovery, development, validation, and sprint-status updates. This process transforms story specs into concrete tasks, artifacts, and validation workflows, reducing manual interpretation and drift.
Maintaining test-driven development and DoD validation requires applying context loading, step sequencing, and quality gates to the story workflow. It ensures traceability and consistent development practices by validating the definition of done before updating the sprint status.
Generating development artifacts requires executing the Dev Story Workflow using a ready story file. It automatically produces a Dev Agent Record, Change Log, and File List, ensuring traceability and quality gates throughout the implementation lifecycle.
Yes, a dev story workflow requires sprint-based workflows with ready-for-dev stories and Epics. It uses these context-filled story specifications to guide task execution, definition of done validation, and subsequent sprint-status updates.
Yes, automated story implementation integrates with sprint status tracking and project context rules. It orchestrates the complete workflow from discovery to review, ensuring consistent development practices while automatically updating the sprint status upon DoD validation.
Story implementation drifts during manual development due to misinterpretation of context and missing validation. Automating the workflow applies step sequencing and context loading to transform story specs into concrete tasks, reducing manual drift.
GenEducationGenerate implementation-ready story files with acceptance criteria, tasks, and dev notes.
salazarsebasExecute story implementations from spec files with red-green-refactor cycles.
ldk-hubExecutes story implementations from spec files across sprint workflows with built-in validation.
thuantan2060Implement story specs via red-green-refactor with test and quality gates.
