メニュー
Build, refresh, or audit a current-state repository orientation map with cited evidence, bounded inference, known gaps, and durable root or area scope.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrate the full spec-driven, test-driven agentic development lifecycle. Use when starting, resuming, auditing, or routing work through the standard RigorLoop workflow. This skill assesses workflow state, enforces artifact order, and keeps exploration, specification, architecture, planning, tests, implementation, review, rationale, verification, PR, and learning connected.
Implement one approved milestone or isolated implementation request with tests or proof first, then hand it to code-review with validation evidence and plan state updated. Use when requirements, scope, and validation commands are clear enough to code. Use bugfix for defect reproduction/fix loops, code-review to review implementation, verify for final readiness, and pr for PR handoff.
Review an implementation slice against the actual diff, governing artifacts, tests, and validation evidence, then record findings or a clean first-pass review. Use after implement hands off a milestone or when implementation review is requested. Use plan-review, spec-review, architecture-review, verify, or pr for those gates instead.
Explain why the agent made each meaningful change by linking the actual diff to the problem, proposal, requirements, architecture decisions, plan milestones, tests, review outcomes, and available validation evidence. Use after implementation and review-resolution, before final verify and PR, or whenever the user asks why code changed.
Create or revise a living execution plan after proposal, spec, and architecture are stable enough to implement. Use for multi-file, multi-component, risky, migration-heavy, or milestone-based work that needs reviewable implementation slices, validation commands, recovery paths, dependencies, and current handoff state. Use spec, test-spec, implement, code-review, verify, or pr for those stages; do not use plan to choose product direction, write code, review diffs, verify branch readiness, or open PRs.
Create a decision-oriented change proposal before spec or plan. Use when the user has a selected direction, explored options, problem statement, or issue that needs problem, goals, non-goals, options, recommendation, risks, rollout, and readiness recorded. Use proposal-review to review an existing proposal; use spec, plan, implement, or verify for downstream work.
| name | project-map |
| version | 0.0.0-test |
| schema-version | skill-readability-v1 |
| description | Build, refresh, or audit a current-state repository orientation map with cited evidence, bounded inference, known gaps, and durable root or area scope. |
| argument-hint | ["repository","area","orientation question","or refresh scope"] |
createrefreshareaauditRequired metadata fields:
Allowed map statuses:
Evidence classes:
Material claim example: a claim that identifies an entry point, trusted boundary, runtime flow, data flow, test surface, CI surface, or downstream reliance point must cite a repository path.
Incidental statement example: a sentence that only names the map purpose or scope does not need a citation.
Every area map must be registered from the root map.
| Area | Map | Scope | Baseline | Freshness | Known gaps |
|---|---|---|---|---|---|
assets/project-map-skeleton.md when creating a new root or area project map.
Fill: metadata fields, applicable sections, evidence paths, known gaps, and area registration fields.
Do not emit unfilled placeholders.- Skill: project-map
- Status: <created|updated|audited|blocked>
- Mode: <create|refresh|area|audit>
- Map scope: <repository|area:slug>