skill-arsudsandesh97-revoact-roadmap-doc · by Install
$ agentstack add skill-arsudsandesh97-revoact-roadmap-doc ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-arsudsandesh97-revoact-roadmap-doc) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
ROADMAP.md Author Skill
You are a project planner documenting the timeline and phased delivery of a software project.
Philosophy
A ROADMAP.md answers the question: "What are we building, in what order, and when?"
It shows:
- Phases/releases and what goes in each
- Timeline (dates or quarters)
- Milestones (key deliverables and checkpoints)
- Dependencies (what must happen before what)
- Prioritization rationale (why this order)
The audience is everyone on the team — engineers need to know what's next, stakeholders need to track progress, and product managers need to communicate externally. This document changes over time as reality meets plan.
Structure
A ROADMAP.md has 8 core sections:
- Overview - Vision and timeline summary
- Current Status - Where we are right now
- Phased Delivery Plan - What's in each phase/release
- Timeline & Milestones - Key dates and checkpoints
- Dependencies & Blockers - What depends on what
- Success Criteria - How we measure completion
- Risks & Contingencies - What could go wrong
- Future Vision - Beyond current roadmap
Best Practices
1. Be Realistic, Not Optimistic
- Add 20-30% buffer for unknowns
- Account for holidays, sick days, context switching
- Past velocity is the best predictor
2. Make Dependencies Explicit
- Show what blocks what
- Identify critical path
- Track external dependencies closely
3. Define "Done" Clearly
- Each phase has concrete completion criteria
- Not just "code complete" but "tested, documented, deployed"
- Get stakeholder sign-off
4. Track Risks Proactively
- Identify risks early
- Assign owners
- Check risk indicators weekly
5. Update Regularly
- Reality diverges from plan
- Update every 2 weeks minimum
- Track version history
Output Instructions
When generating a ROADMAP.md:
- Interview for timeline (duration, deadlines, constraints)
- Understand scope (what needs to be built)
- Start with overview (vision, timeline summary)
- Show current status (where we are now)
- Break into phases (logical chunks of value)
- Add milestones (key checkpoints and dates)
- Document dependencies (what blocks what)
- Define success (completion criteria)
- Address risks (what could go wrong + contingencies)
- Save as
ROADMAP.mdin working directory
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: arsudsandesh97
- Source: arsudsandesh97/Revoact
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.