Skills Roadmap Planning Expert
๐Ÿ“ฆ

Roadmap Planning Expert

Content revision r2 Safe โš™๏ธ External commands

Plan a Realistic Product Roadmap

Teams often overcommit because milestones and capacity are not planned together. This skill helps you turn goals into sized epics, sprint allocations, and clear roadmap decisions.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 76 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 "Roadmap Planning Expert" from https://skillstore.io/skills/andresnaza-roadmap-planning-expert.md and its manifest at https://skillstore.io/api/skills/andresnaza-roadmap-planning-expert/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.

Test it

Using "Roadmap Planning Expert". Plan a quarter for a four-developer team with onboarding and reporting goals.

Expected outcome:

  • A six-sprint sequence of prioritized epics.
  • Milestones with point estimates and owners to confirm.
  • A capacity check that includes a 15% buffer.

Using "Roadmap Planning Expert". Split an 30-point permissions epic into milestones.

Expected outcome:

  • Identity model and role definitions: 10 points.
  • Permission enforcement in core workflows: 12 points.
  • Administration interface and validation: 8 points.

Security Audit

Safe
v11 โ€ข 7/18/2026 Open versioned report

All 18 static findings are false positives caused by Markdown backticks in diagrams, file names, and documented slash commands. The skill contains planning guidance only; no executable shell or Ruby code, network instructions, or prompt-injection language was found.

1
Files scanned
107
Lines analyzed
0
Review items
0
False positives ignored
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: claude 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/andresnaza-roadmap-planning-expert/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

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

AndresNaza. (2026). Roadmap Planning Expert security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/andresnaza-roadmap-planning-expert/audits/11

BibTeX citation

@techreport{andresnaza-andresnaza-roadmap-planning-expert-2026, author = {AndresNaza}, title = {Roadmap Planning Expert security audit report (audit version 11)}, institution = {Skillstore}, year = {2026}, number = {11}, url = {https://skillstore.io/skills/andresnaza-roadmap-planning-expert/audits/11}, 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: "Roadmap Planning Expert security audit report (audit version 11)" version: "unspecified" type: report authors: - name: "AndresNaza" date-released: "2026-07-18" url: "https://skillstore.io/skills/andresnaza-roadmap-planning-expert/audits/11" identifiers: - type: other value: "skillstore:andresnaza-roadmap-planning-expert:audit:11" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Create a quarterly roadmap

Turn product goals into a sequenced set of epics and milestones for the next six sprints.

Balance sprint capacity

Allocate planned milestones to a two-week sprint while retaining buffer for unexpected work.

Prepare an epic delivery plan

Split a large initiative into meaningful milestones that can be estimated and tracked.

Try These Prompts

Start a roadmap
Help me plan a quarterly roadmap for a team of 4 developers. Our goals are faster onboarding and improved reporting.
Break down an epic
Break this epic into 2 to 4 milestones: add team-based permissions to our application. Suggest point estimates and dependencies.
Plan a sprint
Plan the next two-week sprint for 3 developers. We have 48 points of effective capacity after a 15% buffer. These are the available milestones: [list].
Review a constrained roadmap
Review this six-sprint roadmap for capacity conflicts, oversized milestones, and sequencing risks. Propose a revised allocation and explain each change: [roadmap].

Best Practices

  • Confirm goals, constraints, and team availability before estimating work.
  • Split milestones that exceed 25 points before assigning them to a sprint.
  • Review the roadmap with stakeholders and adjust it as delivery information changes.

Avoid

  • Treating point estimates as guaranteed delivery dates.
  • Filling every sprint to full nominal capacity without a buffer.
  • Using roadmap milestones as replacements for detailed engineering specifications.

Frequently Asked Questions

What sprint length does this skill use?
It uses a two-week sprint with 10 working days.
How much capacity is one developer?
The documented model uses 20 points per developer for a two-week sprint.
How large should a milestone be?
Milestones should be meaningful checkpoints and should be split when they exceed 25 points.
Does the skill create detailed specifications?
No. It focuses on strategic planning rather than detailed specifications, PR tracking, or QA.
Should every sprint be fully allocated?
No. The skill recommends a 15% buffer for unexpected work.
Can I synchronize the roadmap with ClickUp?
The documentation describes separate ClickUp push and pull commands for epics and milestones.

Developer Details

Author

AndresNaza

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

80999bf530a7874d7bedf8ce202001ecb4c4f5e0

Maintenance freshness

7/19/2026

Usage

5 downloads ยท 195 views

File structure

๐Ÿ“„ SKILL.md