roadmap-status
Skill93 starsChanged 8 days agoMITView on GitHub
Audit roadmap progress — cross-reference ROADMAP.md with actual codebase implementation
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-breadcrumb-pageSkill
- chaosSkill
- cqrs-patternsSkill
- demo-updateSkill
- host-app-safetySkill
- new-featureSkill
- release-rulesSkill
- releaseSkill
- safety-checkSkill
- testSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read ROADMAP.md and cross-reference each item against the actual codebase to determine what's done vs not done.
- Very specific: line 14
Read ROADMAP.md in the project root.
- Very specific: line 17
Look for relevant files in lib/rails_error_dashboard/, app/, config/
- Very specific: line 18
Check for specs in spec/
- Distinctive: line 19
Check CHANGELOG.md for release notes mentioning the feature
- Very specific: line 20
Look for config options in lib/rails_error_dashboard/configuration.rb
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/roadmap-status — Roadmap Progress Audit
Read ROADMAP.md and cross-reference each item against the actual codebase to determine what's done vs not done.
Steps
- Read the roadmap:
Read
ROADMAP.mdin the project root. - For each roadmap item, check if it's implemented by searching the codebase:
- Look for relevant files in
lib/rails_error_dashboard/,app/,config/ - Check for specs in
spec/ - Check CHANGELOG.md for release notes mentioning the feature
- Look for config options in
lib/rails_error_dashboard/configuration.rb
- Look for relevant files in
- Build a status table with columns:
Status Version Feature Evidence DONE v0.2.0 Cause chain extraction services/cause_chain_extractor.rbDONE v0.3.0 Flexible auth configuration.rb:authenticate_withNOT DONE v0.4.0 Breadcrumb capture No breadcrumb_subscriber.rbfoundPARTIAL v0.5.0 TracePoint locals Config option exists but no implementation - Summarize:
- Total items done / total items
- Next milestone items remaining
- Any items marked as done in ROADMAP but not actually implemented (or vice versa)
Output Format
Print the table in markdown format, grouped by version milestone. Add a summary section at the end.
Key Files to Check
ROADMAP.md— the roadmap itselfCHANGELOG.md— what's been releasedlib/rails_error_dashboard/version.rb— current versionlib/rails_error_dashboard/configuration.rb— config options (100+)lib/rails_error_dashboard/commands/— write operationslib/rails_error_dashboard/queries/— read operationslib/rails_error_dashboard/services/— algorithmsconfig/routes.rb— dashboard endpoints
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.