← ClaudeAtlas

project-maplisted

Draw or update a project map, a single self-contained Hebrew HTML page that shows the project's main parts, the status of each part with evidence, what is blocked and on what, progress toward the next milestone, open decisions waiting on the user, and the recommended next step. Use when the user asks for a project map, project status, progress overview, or "where are we?"; before starting a long autonomous run; and after reaching a milestone. For general plans, reports, or write-ups use html-communication instead.
ShlomiPorush/agent-skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill ShlomiPorush/agent-skills
# Project Map A project map is a living status page for one repository. It answers four questions at a glance: what the project is made of, how far each part has gotten, what is stuck and on what, and what to do next. ## Boundaries - Write only inside `.project-map/` at the repository root. Never change source, configuration, `.gitignore`, `.git/info/exclude`, issues, or pull requests. - Read code, Git history, branches, the working tree, the README and other project documents, and open issues and pull requests when a read-only CLI such as `gh` is available. - Do not run the project's builds, tests, installs, migrations, or servers just to compute status. Use evidence that already exists: commits, files, recorded test results, CI status, issues, and the current conversation. - Keep the map local. Do not publish or upload it unless the user explicitly asks. - Check `git check-ignore -q .project-map`. If the folder is not ignored, do not edit any ignore file. Report it and suggest adding `.project-map/` to the repository's `.gitignore`. - Parts belong to this repository. Other worktrees of the same repository are evidence for the matching parts. Work in another repository that a part depends on appears as that part's `blockedOn` and evidence, not as a part of its own. ## Running it - If you are already running as a subagent, build the map inline. Otherwise, if the host supports background subagents, delegate the map to one at medium effort so the main session keeps working