Skills planning-sprints
📦

planning-sprints

v1.0.0 Content revision r2 Medium Risk ⚙️ External commands

Plan Focused, Achievable Sprints

Teams often overcommit because backlog priority, capacity, and dependencies are considered separately. This skill combines them into a structured sprint plan with measurable goals.

Supports: Claude Codex Code(CC)
📊 71 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "planning-sprints" from https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints.md and its manifest at https://skillstore.io/api/skills/c0ntr0lledcha0s-planning-sprints/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/c0ntr0lledcha0s-planning-sprints.md Signed manifest GET /api/skills/c0ntr0lledcha0s-planning-sprints/manifest Signed lockfile GET /api/skills/c0ntr0lledcha0s-planning-sprints/lockfile

Test it

Using "planning-sprints". Plan a two-week authentication sprint for four engineers with a recent velocity of 34 points.

Expected outcome:

Goal: Release secure sign-in and password recovery. Commitment: 30 points with a four-point buffer. Risks: API review and security testing dependencies.

Using "planning-sprints". Prioritize six backlog items using RICE scores and dependencies.

Expected outcome:

First: login reliability because it has high reach and blocks onboarding. Next: password recovery and session controls. Defer cosmetic profile changes.

Using "planning-sprints". Review a sprint with 16 points remaining after seven of ten days.

Expected outcome:

Status: At risk. Recommended action: move the lowest-value five-point item and escalate the blocking API review today. Preserve the primary sprint goal.

Security Audit

Medium Risk
v10 • 7/23/2026 Open versioned report

All 59 static alerts are false positives caused by Markdown formatting and ordinary sprint terminology. The reviewed files contain no Ruby backtick execution or reconnaissance behavior. A medium semantic risk remains because automatic delegation can trigger state-changing GitHub operations without a clear confirmation checkpoint.

2
Files scanned
776
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
SKILL.md:393-399SKILL.md:438-450SKILL.md:555-558
GitHub mutations lack confirmation gate
Examples delegate board creation, label updates, and backlog reordering, while later guidance allows automatic delegation. External project state could change without explicit confirmation.
The instructions describe board creation, label updates, backlog reordering, and automatic delegation. Actual execution depends on another skill and available credentials.

Risk Factors

⚙️ External commands (50)
SKILL.md:63 SKILL.md:70-76 SKILL.md:76-85 SKILL.md:85-88 SKILL.md:88-90 SKILL.md:90-93 SKILL.md:93-95 SKILL.md:95-103 SKILL.md:103-109 SKILL.md:109-138 SKILL.md:138-146 SKILL.md:146-172 SKILL.md:172-178 SKILL.md:178-185 SKILL.md:185-192 SKILL.md:192-198 SKILL.md:198-201 SKILL.md:201-209 SKILL.md:209-212 SKILL.md:212-219 SKILL.md:219-224 SKILL.md:224-234 SKILL.md:234-237 SKILL.md:237-245 SKILL.md:245-248 SKILL.md:248-254 SKILL.md:254-259 SKILL.md:259-264 SKILL.md:264-267 SKILL.md:267-275 SKILL.md:275-280 SKILL.md:280-284 SKILL.md:284-287 SKILL.md:287-299 SKILL.md:299-302 SKILL.md:302-308 SKILL.md:308-313 SKILL.md:313-321 SKILL.md:321-324 SKILL.md:324-327 SKILL.md:327-335 SKILL.md:335-344 SKILL.md:344-347 SKILL.md:347-361 SKILL.md:361-406 SKILL.md:406-413 SKILL.md:413-451 SKILL.md:451-458 SKILL.md:458-503 SKILL.md:503-556
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/c0ntr0lledcha0s-planning-sprints/security.svg)](https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/c0ntr0lledcha0s-planning-sprints/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/c0ntr0lledcha0s-planning-sprints.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

C0ntr0lledCha0s. (2026). planning-sprints security audit report (audit version 10) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints/audits/10

BibTeX citation

@techreport{c0ntr0lledcha0s-c0ntr0lledcha0s-planning-sprints-2026, author = {C0ntr0lledCha0s}, title = {planning-sprints security audit report (audit version 10)}, institution = {Skillstore}, year = {2026}, number = {10}, url = {https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints/audits/10}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "planning-sprints security audit report (audit version 10)" version: "1.0.0" type: report authors: - name: "C0ntr0lledCha0s" date-released: "2026-07-23" url: "https://skillstore.io/skills/c0ntr0lledcha0s-planning-sprints/audits/10" identifiers: - type: other value: "skillstore:c0ntr0lledcha0s-planning-sprints:audit:10" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
87
Content
70
Community
78
Spec Compliance

What You Can Build

Plan the next product sprint

Turn a prioritized backlog and product objective into a focused sprint goal, balanced scope, and clear success criteria.

Set a realistic team commitment

Combine recent velocity, leave, meetings, and team changes to recommend a sustainable sprint commitment.

Recover a sprint at risk

Assess burndown, blockers, and remaining scope, then prepare options for descoping or unblocking work.

Try These Prompts

Create a basic sprint plan 
Create a two-week sprint plan for [team] using this backlog: [items]. Team capacity is [availability], and recent velocity is [points].
Prioritize a backlog 
Prioritize [backlog items] using [RICE, MoSCoW, WSJF, or value versus effort]. Explain each score, dependency, risk, and recommended sprint order.
Review sprint health 
Review sprint [name] at day [number] using completed, active, blocked, and remaining work. Identify delivery risk and recommend specific scope changes.
Compare advanced scope options 
Build a sprint plan from [backlog], [velocity history], [availability], and [strategic goals]. Compare two scope options, test dependencies, and define measurable success criteria.

Best Practices

  • Provide current backlog details, recent velocity, team availability, and sprint dates before requesting a plan.
  • Validate estimates and dependencies with the delivery team before committing the sprint.
  • Reserve capacity for uncertainty and update the plan when approved scope changes occur.

Avoid

  • Do not treat generated priorities as final without product and engineering review.
  • Do not compare velocity across teams because story-point scales differ.
  • Do not allow automatic board, label, or file changes without explicit confirmation.

Frequently Asked Questions

Which planning methods does this skill support?
It supports RICE, MoSCoW, WSJF, value-versus-effort analysis, velocity review, and capacity planning.
Can it read my GitHub backlog?
Yes, when the gh CLI is authenticated and repository access is available. Review repository scope before running commands.
Does it create or update GitHub boards?
The instructions can delegate GitHub operations to another skill. Require confirmation before any board, label, or backlog change.
How much capacity should a sprint use?
The guidance recommends approximately 80 to 90 percent of calculated capacity, with room for uncertainty and urgent work.
Are the referenced planning scripts included?
No. This package contains the main skill file and one sprint plan template, but the referenced calculator scripts are absent.
Can this skill guarantee sprint delivery?
No. It structures planning decisions, but delivery still depends on estimates, dependencies, team availability, and changing conditions.

Developer Details

License

MIT

Author version

v1.0.0

Skillstore revision

r2

Repository

https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations/tree/main/project-manager/skills/planning-sprints

Ref

a39a91716eadede5f4cdefd78178fed4e837a128

Maintenance freshness

7/24/2026

Usage

8 downloads · 207 views

File structure

📄 SKILL.md

📁 templates/

📄 sprint-plan-template.md