AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Roadmap Management

skill-theseus-run-theseus-roadmap-management · by theseus-run

Use when creating, updating, reviewing, or promoting Theseus roadmap items, including public roadmap notes, internal roadmap status maps, planning lanes, GitHub issue readiness, and OSS roadmap hygiene.

↗ Website ↗ Repository
— No reviews yet
0 installs
22 views
0.0% view→install

Install

$ agentstack add skill-theseus-run-theseus-roadmap-management

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-theseus-run-theseus-roadmap-management)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Roadmap Management? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Theseus Roadmap Management

Use this skill when roadmap or planning work changes what Theseus says it is building next.

Roadmap work is status management, not aspiration capture. Keep current truth, planned work, research, and rejected paths separate.

Read Order

Start with:

  1. docs/direction/roadmap.md
  2. docs/maps/roadmap-status-map.md
  3. docs/maps/runtime-truth-map.md
  4. docs/maps/not-real-yet.md
  5. the owning concept note for the roadmap item

If an item concerns implementation, verify against source before marking it shipped, active, or next.

Roadmap Artifacts

  • docs/direction/roadmap.md: concise public-facing roadmap.
  • docs/maps/roadmap-status-map.md: internal evidence table and promotion state.
  • GitHub issues: execution units only after the item is actionable.
  • GitHub milestones/projects: sequencing containers, not doctrine.

Do not put loose ideation in the roadmap. Move it to docs/brainstorms or docs/drafts first.

Status Vocabulary

Use one status per item:

  • shipped: implemented and verified.
  • active: currently being built.
  • next: intended soon and clear enough to plan.
  • designed: accepted direction, not scheduled.
  • research: needs investigation, prototype, or decision.
  • blocked: dependency or unresolved decision is known.
  • parked: not rejected, but not worth attention now.
  • rejected: deliberately not doing.

Avoid future. It hides whether an item is designed, research, blocked, or parked.

Promotion Pipeline

brainstorm -> draft -> designed -> next -> active -> shipped

Promotion rules:

  • Do not promote directly from brainstorm to active.
  • Do not mark next without a done when test.
  • Do not mark active without an owner and evidence that work has started.
  • Do not mark shipped unless code, tests/checks, and docs agree.
  • When promoting or demoting, update roadmap-status-map.md in the same pass.

Item Shape

Every roadmap-ready item needs:

  • status
  • owner
  • source docs
  • evidence or current implementation note
  • dependency or blocker, if any
  • done when criteria

If done when cannot be written, the item belongs in research, drafts, or brainstorms, not next.

OSS Posture

For public docs:

  • Prefer Now / Next / Later / Not Planned over dates.
  • Publish less than the internal status map knows.
  • State non-promises explicitly.
  • Do not imply timelines unless the project intends to carry timeline pressure.
  • Keep roadmap items tied to user-visible or contributor-visible value.

Verification

After roadmap doc edits, run:

bun run docs:check

Use docs-management rules for links, frontmatter, folder placement, and status separation.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

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.

More in Developer Tools