Skip to content
Back to skills

Maintain Project Roadmap

ASecurity

Maintain ROADMAP.md as the planning member of the canonical four-document repository suite.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsrailsgitdocumentation

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add gaelic-ghost/socket --skill maintain-project-roadmap --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Maintain Project Roadmap?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Maintain Project Roadmap
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gaelic-ghost-maintain-project-roadmap/badge)](https://www.skillsdirectory.com/skills/gaelic-ghost-maintain-project-roadmap)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: maintain-project-roadmap
description: Maintain ROADMAP.md as the planning member of the canonical four-document repository suite.
---

# Maintain Project Roadmap

## Purpose

Keep checklist-style `ROADMAP.md` milestones, tickets, progress, backlog, and
history structurally consistent while the entire canonical documentation suite
is maintained together.

## Commands

The only documentation commands are:

```text
just docs-check
just docs-apply
```

Both always process README, CONTRIBUTING, AGENTS, and ROADMAP. Ticket mutation,
source collection, and GitHub issue collection are not separate command modes;
the managed full-document pass owns deterministic roadmap normalization.

## Managed Contract

- `assets/document.contract.json` fixes sections, milestone subsections,
  allowed statuses, and a small fixed alias set.
- `assets/ROADMAP.template.md` supplies bootstrap and missing-section content.
- Repositories cannot customize status vocabulary, headings, aliases, order,
  or automatic-fix policy.

## ROADMAP Ownership

ROADMAP owns vision, product principles, milestone progress, milestone scope,
tickets, exit criteria, small tickets, backlog candidates, and notable planning
history. Setup and procedure belong to CONTRIBUTING or maintainer docs; safety
policy belongs to AGENTS.

Milestone Progress and the table of contents are regenerated from the canonical
milestone sections. Missing milestone subsections are added from the managed
template. Known status aliases normalize deterministically; unknown semantic
states remain blocking findings rather than being invented.

## Deterministic Workflow

Use `just docs-check` for the full no-write audit and `just docs-apply` for the
atomic, byte-idempotent four-document normalization transaction.

## Guardrails

- Never maintain or mutate ROADMAP independently of the full document suite.
- Never invent milestone status, scope, ticket details, or completion claims.
- Never add customization or alternate roadmap formats.
- Never commit, push, or open a pull request as part of documentation upkeep.

## References

- `assets/document.contract.json`
- `assets/ROADMAP.template.md`

Files in this skill

  • SKILL.md2.1 KB
  • agents/openai.yaml868 B
  • assets/ROADMAP.template.md1.5 KB
  • assets/document.contract.json1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…