Menu
{{ ƔƔƔ }} Create or update a README — project root or any directory
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
{{ 𝚫𝚫𝚫 }} Rebuild roadmap-system.zip, the distributable snapshot of the roadmap tooling (scripts, HTML template, conventions reference, and every roadmap-touching skill, including this one).
{{ 𝛀𝛀𝛀 }} Create a project roadmap in the rich phase-array format — roadmaps.json as source of truth plus a PHASE task list and prose overview
{{ 𝛀𝛀𝛀 }} Recompute and synchronise roadmap task statuses across roadmaps.json and its projections, with optional codebase reconciliation
{{ 𝛀𝛀𝛀 }} Add a task to a rich-format project roadmap with correct ID, dependency wiring, and graph integrity — ID assignment, status computation, dependency edges in both directions, and no unconnected islands.
Git workflow: branch management, commit conventions, PR patterns, conflict resolution.
{{ 𝛀𝛀𝛀 }} Review a pull request and post it as a GitHub review
| name | Docs: Readme |
| description | {{ ƔƔƔ }} Create or update a README — project root or any directory |
| when_to_use | When a project or directory has no README, or its existing one no longer matches the current structure or setup steps. |
| model | sonnet |
| disable-model-invocation | true |
| allowed-tools | ["Read","Glob","Grep","Write","Edit","Bash(git:*)","Bash(~/.claude/library/scripts/git-doc-history.sh:*)"] |
| arguments | ["mode","target"] |
| argument-hint | [create|update] [directory, default ./] |
Replaces the former doc-readme-create / doc-readme-create-sub / doc-readme-update trio: $mode picks the verb, $target picks the directory (project root when empty). If $mode is empty, infer it: README exists at the target → update; absent → create. Say which you inferred.
~/.claude/library/templates/readme-root.md for the project root, readme-sub.md for a sub-directory. Each {{ slot }} describes its content; drop sections that do not apply, never invent content to fill one.Resolve the README ($target/README.md, default ./README.md). If it does not exist, say so and offer create mode instead.
Read it for structure and style, then gather what changed in one command:
"$HOME"/.claude/library/scripts/git-doc-history.sh $target/README.md $target
It prints the commits, file changes and diff stat since the README was last touched — analyse that dump rather than running exploratory git calls.
Identify what needs updating: outdated descriptions, undocumented additions, removed content to clean up, structural changes.
Generate targeted updates preserving the existing structure and style; show a diff; apply on approval.
If the changes are minor, say so — don't invent updates for the sake of it. Prefer surgical edits over rewrites; don't remove content unless genuinely obsolete.