skills.rest
MagicBowen
MagicBowenCOMMUNITY
Explore all skills by this author →
GitHub

dogent-story-implementation

Automate Dogent story implementation, unit tests, and sprint doc updates.

4|Updated Nov 14, 2025
Search Tags:#workflow#testing#unit-tests#story-implementation#sprint-management#dogent
One-click install
npx skills add https://github.com/MagicBowen/dogent --skill dogent-story-implementation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogent-story-implementation
Source: https://github.com/MagicBowen/dogent/tree/main/.agents/skills/dogent-story-implementation
Command: npx skills add https://github.com/MagicBowen/dogent --skill dogent-story-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Implementing Dogent release stories ensures code changes align with the repo workflow, include automated tests, and keep sprint tracking up to date for UAT readiness.

Core Features & Use Cases

  • Sequential story implementation following the sprint plan, with tests for changed functions.
  • Add or update automated unit tests and run targeted test suites to validate changes.
  • Update sprint documentation (dev/sprint_plan.md and dev/sprint_uat.md) to reflect delivered work that awaits manual UAT.

Quick Start

Read the target story in dev/sprint_plan.md, implement it with minimal scope, run the unittest suite, and update the sprint tracking docs accordingly.

Frequently Asked Questions about dogent-story-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sprint story implementation and unit testing end-to-end?▼

Automate sprint story implementation by sequentially executing minimal scoped code changes, adding automated unit tests for changed functions, and running targeted test suites to validate code changes.

How does sprint management workflow update tracking documents after story implementation?▼

Sprint management workflow updates tracking documents by modifying dev/sprint_plan.md and dev/sprint_uat.md to reflect delivered work that has passed unit tests and awaits manual UAT.

What is the best way to ensure minimal scoped code changes during story implementation?▼

Ensure minimal scoped code changes by reading the target story in dev/sprint_plan.md, implementing only the specified requirements, and validating the scoped modifications with automated unit tests.

Can I run targeted unit tests for specific changed functions in a release workflow?▼

Run targeted unit tests for specific changed functions by adding or updating automated tests during story implementation and executing the unittest suite to validate the release workflow changes.

Do I need to manually update sprint tracking docs after implementing a story?▼

You do not need to manually update sprint tracking docs because the workflow automatically updates dev/sprint_plan.md and dev/sprint_uat.md to reflect delivered story work awaiting UAT.

Why does story implementation require updating both sprint plan and UAT documents?▼

Story implementation requires updating both sprint plan and UAT documents to maintain accurate sprint tracking for delivered code changes and signal UAT readiness for manual validation.

Related Skills

Explore More Software Engineering Skills→
amitmishra-bylddamitmishra-byldd

bmad-dev-story

Execute story implementation from context-filled spec files with status transitions.

Community
Advanced
MagicBowenMagicBowen
4

dogent-story-acceptance

Fix post-UAT issues and update sprint UAT documents with retest guidance.

Community
Advanced
arbazkhan971arbazkhan971
26

ship

Automate shipping code changes with pre-ship checks, dry-run, execution, verification, and rollback.

Community
Advanced
tabooestabooes
1

user-story-splitting

Split large user stories into smaller independent stories using an 8-pattern framework.

Community
Intermediate