sprint-manifest

Promote validated PRDs into a sprint and generate an aggregated sprint-manifest.md.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill sprint-manifest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-manifest
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/sprint-manifest
Command: npx skills add https://github.com/russosalv/NONoise --skill sprint-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The sprint-manifest skill coordinates the promotion of validated PRDs into a sprint and creates a single aggregated sprint-manifest.md that guides teams through macro-functional tasks, dependencies, and impact analysis.

Core Features & Use Cases

  • Promotes validated PRDs from docs/prd/<area>/ to docs/sprints/Sprint-N/<area>/ and updates their status to promoted.
  • Generates or updates one aggregated Sprint Manifest at docs/sprints/Sprint-N/sprint-manifest.md, listing PRDs, deriving user stories, and breaking work into macro tasks with CL1/CL2/CL3 confidences.
  • Runs impact analysis when a new PRD is added to an open sprint, and appends changelog entries.
  • Serves as the seed for downstream work-item export skills and aligns with the macro-granularity principle.

Quick Start

Run sprint-manifest to promote validated PRDs and generate the sprint manifest for the target sprint.

Frequently Asked Questions about sprint-manifest

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

FAQPage Schema
How do I promote validated PRDs into a unified sprint manifest?

To promote validated PRDs into a sprint manifest, the skill compiles multiple PRDs from docs/prd/<area>/ into docs/sprints/Sprint-N/<area>/, updates their status to promoted, and generates a single aggregated sprint-manifest.md file.

What is a sprint manifest and how does it coordinate macro tasks?

A sprint manifest is an aggregated markdown file that coordinates macro-functional tasks and dependencies across promoted PRDs, deriving user stories and breaking work into macro tasks with CL1/CL2/CL3 confidence tagging.

How do I run impact analysis when adding a new PRD to an open sprint?

When adding a new PRD to an open sprint, the skill automatically runs impact analysis against the existing sprint manifest and appends changelog entries to track dependencies and coordinate macro tasks.

Can I update an existing sprint manifest after promoting new PRDs?

Yes, you can update an existing sprint manifest by regenerating it from newly promoted PRDs, ensuring the aggregated file reflects the latest macro tasks, dependencies, and impact analysis.

Does sprint planning require CL1, CL2, and CL3 confidence tagging for macro tasks?

Sprint planning requires CL1/CL2/CL3 confidence tagging for macro tasks to satisfy macro-granularity principles, allowing teams to assess the certainty and impact of derived user stories within the sprint manifest.

What is the best way to coordinate dependencies across multiple PRDs in agile planning?

The best way to coordinate dependencies across multiple PRDs is by compiling a single aggregated sprint manifest that maps macro-functional tasks, runs impact analysis, and aligns work under unified macro-granularity.