Menu
Map the current repository into a durable project description at `.project/PROJECT.md`.
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
Design a target architecture for a new system — module boundaries, dependency rules, seams, and build order — from its requirements. Reports a blueprint; changes nothing.
Analyze an existing codebase's architecture and produce a sequenced refactoring plan — assess module boundaries, dependency structure, and layering, then lay out ordered, risk-tagged steps. Language-agnostic. Reports a plan; changes nothing.
Turn a goal or another command's output into an ordered task roadmap.
Find the root cause of a failure with the scientific method — reproduce, isolate, fix, then prove it.
Interview the user relentlessly about a plan or design until reaching shared understanding.
Run an extremely strict maintainability + single-source-of-truth review of code changes — abstraction quality, file sprawl, spaghetti-condition growth, and duplicate/competing implementations. Reports findings by default; `--fix` applies the mechanical, unambiguous ones — structural/code-judo restructurings rest on judgment and stay reported.
| name | ds-project-map |
| description | Map the current repository into a durable project description at `.project/PROJECT.md`. |
| disable-model-invocation | true |
When invoked, read the actual codebase and write (or refresh) .project/PROJECT.md — the stable description a fresh session reads to understand the project. Describe what exists; do not invent direction or make technical decisions.
.project/ if it does not exist.package.json, go.mod, etc.), and entry points. Search to find the major pieces; read scoped regions, not whole files. Read enough to be accurate, no more — the map is identifiers and one-liners, not a digest of every file..project/PROJECT.md with these sections:
.project/PROJECT.md already exists, treat it as partly human-authored. Refresh the code-derived sections (Stack, Repo map) to match the current source — but before overwriting, compare what you would generate against what's already there. Anything present that you would not re-derive from the code — a manually-added project truth, a constraint or rule not visible in the source, a custom section, hand-written Overview prose — is human-added knowledge. List those items and ask whether to keep, update, or drop each one before you write. Never silently discard them; default to keeping..project/PLAN.md.Display the path and a one-line summary of what changed (created, or which sections were refreshed).