work

Coordinate sprint backlog items through implementer, reviewer, and CI validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/krystophny/prompts --skill work-krystophny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/krystophny/prompts/tree/main/skills/work
Command: npx skills add https://github.com/krystophny/prompts --skill work-krystophny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint implementation coordinates end-to-end delivery by structuring a fixed chain of roles and CI checks to ensure backlog items reach a merged, validated state.

Core Features & Use Cases

  • Orchestrates a max -> implementer -> reviewer -> max handoff to enforce role separation and accountability.
  • Integrates CI validation to guarantee code quality and repository health before merging.
  • Supports sprint cycles, backlog completion, and deterministic delivery with minimal manual prompts.

Quick Start

Initiate a sprint implementation run using the defined handoff chain and CI gates.

Frequently Asked Questions about work

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

FAQPage Schema
How do I automate sprint backlog execution with CI validation?

Automate sprint backlog execution by passing work items through a max, implementer, and reviewer chain with CI validation. Items become fully implemented, tested, and merged only after CI success to ensure deterministic delivery.

What is the best way to enforce separation of concerns during sprint implementation?

Enforce separation of concerns during sprint implementation by orchestrating a fixed max to implementer to reviewer handoff chain. This strict role separation ensures accountability and deterministic backlog completion across sprint cycles.

How does CI validation work with sprint backlog automation?

CI validation works with sprint backlog automation by acting as a gate before merging. Code must pass CI checks guaranteeing repository health and code quality, ensuring backlog items reach a fully tested and validated state.

Can I run non-interactive workflow automation for backlog completion?

Yes, you can run non-interactive workflow automation for backlog completion. The execution minimizes manual prompts and ensures determinism by passing work items through the automated handoff chain and CI gates without interaction.

Do I need manual prompts to coordinate code review in a sprint workflow?

No, manual prompts are not needed to coordinate code review in a sprint workflow. The automated reviewer role handles validation within the handoff chain, enforcing code quality and non-interactive execution across sprint cycles.

Why use a fixed role chain for sprint backlog automation instead of manual task assignment?

Use a fixed role chain for sprint backlog automation to ensure strict separation of concerns and deterministic delivery. Unlike manual task assignment, the automated max, implementer, and reviewer handoff enforces accountability and CI validation.