Skills agile-planning

📦

agile-planning

Content revision r1 Safe ⚙️ External commands

Plan Agile Releases with Sprint Roadmaps

Release planning often breaks down when timelines, tasks, and dependencies are scattered. This skill turns project context into sprint schedules, task codes, milestones, and roadmap views.

Supports: Claude Codex Code(CC)

📊 74 Adequate

📊 74 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 "agile-planning" from https://skillstore.io/skills/emz1998-agile-planning.md and its manifest at https://skillstore.io/api/skills/emz1998-agile-planning/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/emz1998-agile-planning.md Signed manifest GET /api/skills/emz1998-agile-planning/manifest Signed lockfile GET /api/skills/emz1998-agile-planning/lockfile

Test it

Using "agile-planning". Plan an eight-week mobile app MVP for two developers.

Expected outcome:

A four-sprint release plan with user foundation, activity tracking, visualization, and launch preparation phases.

Using "agile-planning". Create a six-sprint checkout release roadmap for an e-commerce platform.

Expected outcome:

A quarterly roadmap with payment foundation, checkout UI, payment integration, testing, beta launch, and production release.

Using "agile-planning". Break this backlog into sprints and show dependencies.

Expected outcome:

A sprint schedule with unique task codes, dependency notes, milestones, and a stakeholder-friendly roadmap summary.

Security Audit

Safe

v4 • 7/6/2026 Open versioned report

All six static findings are false positives after contextual review. The flagged external command patterns are markdown code fences and examples, and the reconnaissance flag points to task-writing guidance.

3

Files scanned

756

Lines analyzed

0

Review items

0

False positives ignored

Risk Factors

⚙️ External commands (5)

SKILL.md:77-118 SKILL.md:118-164 SKILL.md:164-269 SKILL.md:269-273 SKILL.md:273-336

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

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/emz1998-agile-planning/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/emz1998-agile-planning.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

Emz1998. (2026). agile-planning security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emz1998-agile-planning/audits/4

BibTeX citation

@techreport{emz1998-emz1998-agile-planning-2026,
  author = {Emz1998},
  title = {agile-planning security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/emz1998-agile-planning/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "agile-planning security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "Emz1998"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/emz1998-agile-planning/audits/4"
identifiers:
  - type: other
    value: "skillstore:emz1998-agile-planning:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

41

Architecture

85

Maintainability

87

Content

71

Community

83

Spec Compliance

What You Can Build

Plan a Product Release

Turn scope, timeline, and team size into a sprint plan with milestones and dependencies.

Coordinate Engineering Delivery

Break implementation work into coded tasks that teams can discuss during sprint planning.

Communicate a Roadmap

Summarize upcoming sprint outcomes by month, quarter, or project phase for stakeholders.

Try These Prompts

Draft a Basic Release Plan

Create an agile release plan for [project]. Timeline: [duration]. Team: [team size]. Include sprints, task codes, dependencies, and milestones.

Turn Backlog Into Sprints

Convert this backlog into two-week sprints with SPRINT-001 and T-001 codes: [backlog]. Show dependencies and release checkpoints.

Build a Stakeholder Roadmap

Create a roadmap for [release name] using these priorities: [priorities]. Group sprints by month and highlight alpha, beta, and production milestones.

Adjust for Risk and Capacity

Revise this release plan for a team of [team size] with [capacity constraints]. Front-load risky work and add a buffer sprint.

Best Practices

Provide scope, timeline, team size, and priorities before asking for a plan.
Review dependencies and milestones with delivery leads before sharing the roadmap.
Keep task codes stable after publication so teams can discuss work consistently.

Avoid

Asking for a plan without timeline or team capacity.
Treating generated dates as commitments before team review.
Using the skill to replace backlog grooming or product discovery.

Frequently Asked Questions

Will this skill create Jira tickets?

No. It creates planned task codes and descriptions that you can copy into project tools.

Can it handle short and long releases?

Yes. The references include short release templates and longer release patterns with phases.

Does it create unique sprint and task codes?

Yes. It uses sequential sprint codes and task codes across the full release.

Can I provide my own dates?

Yes. Provide start dates, milestone dates, or sprint duration so the plan fits your calendar.

Will it estimate capacity automatically?

It can apply simple capacity guidance when you provide team size, sprint length, and constraints.

Should I include confidential roadmap details?

Only include sensitive plans if your AI environment is approved for that information.

Developer Details

Author

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Emz1998/nexly-notes/tree/main/archive/agile-planning

Ref

a06681402992ceae98ba04d54cfd4ab004862696

Maintenance freshness

7/18/2026

Usage

7 downloads · 249 views

File structure

📁 references/

📄 sprint-guide.md

📄 template.md

More from Emz1998

code-instructor

Teach Code by Building Apps

Learning code can feel abstract when examples are disconnected from real projects. This skill teaches concepts while building working applications step by step.

Coding & Development View

brainstorming-features

Brainstorm App Features with Structured Ideas

Teams need practical feature ideas that connect user value, feasibility, and metrics. This skill guides structured brainstorming for web and mobile app planning.

Productivity View

writing-page-layout

Create compact Next.js page layouts

Next.js page files can become hard to maintain when layout, types, and page logic grow together. This skill guides Claude, Codex, and Claude Code to produce modular page.tsx layouts with separated types.

Coding & Development View

tasks-generator

Generate Project Task Roadmaps

Project teams often struggle to turn specifications into clear implementation work. This skill converts specs into phased tasks with dependencies and verification steps.

Productivity View

implementation-review

Review Implementations Before Commit

Teams can miss plan flaws or code issues when workflow steps move quickly. This skill routes completed plans and implementations to review agents before the next phase.

Coding & Development View

writing-types

Write Modular Next.js Types

Next.js projects can collect large type files that are hard to maintain. This skill guides Claude, Codex, and Claude Code to write small TypeScript types and interfaces in srs/types.

Coding & Development View

sprint-planner

Plan Agile Sprints With Clear Capacity

by shubhamsaboo

Sprint planning often stalls when scope, estimates, and capacity are unclear. This skill guides Claude, Codex, and Claude Code to create sprint goals, backlog tables, risks, and done criteria.

Productivity View

task-planning

Plan Agile Tasks and User Stories

by supercent-io

Teams often receive broad feature requests without clear tasks, priorities, or acceptance criteria. This skill turns feature ideas into user stories, sprint backlog items, dependencies, and Definition of Done checks.

Productivity View

planning-action

Build Actionable Execution Plans

by BellaBe

Vague goals are hard to convert into work. This skill turns a decision into phases, milestones, dependencies, risks, and checkpoints.

Productivity View

task-estimation

Estimate Agile Tasks With Story Points

by supercent-io

Teams need consistent estimates for sprint planning and roadmaps. This skill guides story points, planning poker, sizing, risks, and task breakdowns.

Productivity View

agile-ceremonies

Run Agile Ceremonies

by 89jobrien

Agile teams need concise ceremonies that keep work visible and action items clear. This skill provides standup, retrospective, sprint progress, and team health formats for Claude, Codex, and Claude Code.

Productivity View

agile-product-owner

Create Agile Stories and Sprint Plans

by alirezarezvani

Product teams often lose time turning ideas into clear, testable backlog items. This skill helps create user stories, acceptance criteria, estimates, and capacity-based sprint plans.

Productivity View