sprint

Automate PRD evolution by sprint with requirement spine alignment and design amendments.

3|Updated Jun 10, 2026

Search Tags:#code generation #system architecture #sprint management #PRD evolution #design amendment

Ready to run

npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill sprint-cwijayasundara

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/cwijayasundara/claude_harness_eng_v5/tree/main/.claude/skills/sprint
Command: npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill sprint-cwijayasundara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the evolution of a system PRD by sprint, ensuring that each new PRD is grounded against the prior requirement spine and amends the living design baseline with human review.

Core Features & Use Cases

Grounds new PRDs: Aligns new PRDs against the prior sprint's requirement spine.
Automated Design Amendment: Amends the living design baseline without regenerating the architecture.
Human Review: Ensures that design amendments are reviewable and approved before proceeding.
Use Case: Ideal for evolving an existing architecture with multiple stories, where a full PRD is required.

Quick Start

Run the sprint skill with the PRD file: /sprint prd-sprint2.md

Frequently Asked Questions about sprint

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

FAQPage Schema

How do I evolve a system PRD across multiple sprints without regenerating the architecture?▼

To evolve a system PRD across sprints without regenerating architecture, you automate design amendments by aligning new PRDs against the prior sprint's requirement spine. This amends the living design baseline directly, preserving the existing architecture while integrating new stories.

What is automated design amendment for living PRD baselines?▼

Automated design amendment for living PRD baselines is the process of updating an existing system design with new sprint requirements. It processes requirement deltas against the current baseline, ensuring architecture evolves incrementally rather than through full regeneration.

How do I align a new PRD against a prior sprint's requirement spine?▼

You align a new PRD against a prior requirement spine by running an automated sprint workflow. The system grounds the new PRD file against the previous sprint's established requirements, identifying deltas to amend the living design baseline.

Does PRD evolution support human review before amending the system design?▼

Yes, PRD evolution supports human review before amending the system design. The workflow ensures that all automated design amendments are reviewable and must be approved by a human before they are integrated into the living design baseline.

Can I generate test plans when evolving a system PRD by sprint?▼

Yes, you can generate test plans when evolving a system PRD by sprint. The automated workflow processes requirement spine alignments and design amendments, then generates corresponding test plans to validate the newly integrated features.

What's the best way to manage multiple stories for an existing architecture?▼

The best way to manage multiple stories for an existing architecture is to use an automated sprint workflow that requires a full PRD. This grounds each story against the prior requirement spine and amends the living design baseline with human review.