dogent

Archive completed Dogent release history from active planning files into `dev/archives`. Use when the user asks to archive old/history requirements, sprint design, sprint plan, or sprint UAT sections from `dev/requirement.md`, `dev/sprint_design.md`, `dev/sprint_plan.md`, and `dev/sprint_uat.md`.

Create or optimize Dogent document templates in the standard template-skill directory format. Use whenever the user asks to create a new document template, improve an existing template, restructure template metadata, or rewrite template guidance for Dogent's `.dogent/templates`, `~/.dogent/templates`, or built-in `dogent/templates` locations.

General-purpose template for professional documents when no specialized template is selected.

Produce a credible, reproducible research report grounded in high-quality sources with verifiable citations and clear separation of evidence, analysis, and recommendations.

A resume format optimized for experienced technical professionals that emphasizes work experience, measurable impact, and leadership.

A framework for producing high-quality technical blog posts that balance technical depth, readability, and professional rigor.

Publish an accepted Dogent release according to `dev/package.md`. Use when the user asks to update `CHANGELOG.md`, bump the version in `pyproject.toml`, commit and tag the release, build artifacts, or publish the release to GitHub.

Implement approved Dogent release stories under the repo workflow. Use when the user asks to code according to `dev/sprint_design.md` or `dev/sprint_plan.md`, add automated tests for changed functions, run the unittest suite, or update `dev/sprint_uat.md` and `dev/sprint_plan.md` to reflect delivered work that is still pending acceptance.

Analyze and plan Dogent release requirements into the repo tracking docs. Use when the user says `dev/requirement.md` was updated, asks to read a release requirement, design it, identify contradictions or missing decisions, append release design to `dev/sprint_design.md`, split approved work into dependency-ordered user stories in `dev/sprint_plan.md`, or append manual UAT cases to `dev/sprint_uat.md` before implementation.

Process Dogent manual UAT feedback after the user updates `dev/sprint_uat.md`. Use when the user asks to fix bugs found in UAT, update `dev/sprint_uat.md` for retest, or mark current-release stories accepted in `dev/sprint_uat.md` and `dev/sprint_plan.md` after all UATs pass.