sprint-okr-planning

Name: sprint-okr-planning
Availability: InStock
Author: Valynt

Generate multi-sprint OKR plans with key results and risk flags from roadmap and debt data.

Updated Nov 17, 2025

Search Tags:#planning #dependencies #roadmap #traceability #okr #sprint #risk

Ready to run

npx skills add https://github.com/Valynt/ValueOS --skill sprint-okr-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-okr-planning
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/sprint-okr-planning
Command: npx skills add https://github.com/Valynt/ValueOS --skill sprint-okr-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sprint planning for multi-sprint roadmaps anchored to codebase debt, dependencies, and risk, enabling teams to align objectives and resources.

Core Features & Use Cases

Generates formal sprint OKR planning documents covering ≥4 sprints with an objective, 3–5 key results per sprint, and risk flags.
Anchors planning to debt items and traceability data, and sequences sprints by architectural dependencies.
Produces cross-functional handoff notes, architectural rationale, and acceptance criteria.

Quick Start

Provide a four-sprint OKR plan grounded in the current debt and traceability context.

Frequently Asked Questions about sprint-okr-planning

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

FAQPage Schema

How do I plan sprint OKRs based on codebase debt and dependencies?▼

Multi-sprint OKR planning requires reading `.windsurf/context/*`, `sprint-roadmap.md`, and `docs/` references to generate formal documents covering four or more sprints with an objective, multiple key results, and cross-functional handoff notes.

What is the best way to sequence a multi-sprint roadmap using traceability data?▼

Sequencing a multi-sprint roadmap using traceability data involves linking objectives, key results, and risk flags across teams based on architectural dependencies. This approach ensures sprints are ordered to resolve debt items before building dependent features.

Can I generate acceptance criteria and handoff notes for a four-sprint OKR plan?▼

Yes, you can generate formal sprint OKR planning documents that include cross-functional handoff notes, architectural rationale, and acceptance criteria. The plan covers four or more sprints with an objective and three to five key results per sprint.

Does sprint OKR planning work with existing roadmap and context files?▼

Sprint OKR planning requires no external dependencies but needs existing context files including `.windsurf/context/*`, `sprint-roadmap.md`, and `docs/` references to generate structured OKRs and acceptance criteria based on current debt and traceability data.

What happens to sprint planning if traceability gaps and debt items are not sequenced by dependencies?▼

Sprint OKR planning is limited by the quality of context files in `.windsurf/context/*` and `sprint-roadmap.md`. Without accurate debt and traceability data, the generated OKRs and risk flags may not reflect true architectural dependencies.