sp-map-scan

Builds a value-weighted evidence baseline of a brownfield codebase for graph reconstruction.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-map-scan-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-map-scan
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-map-scan
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-map-scan-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Brownfield projects lack a reliable, graph-native understanding of their own codebase, so downstream planning and navigation workflows operate on guesswork. This Skill enumerates the full project file universe, classifies files by value tier, deep-scans the highest-value evidence, and publishes provisional nodes, edges, and coverage artifacts that a later build step turns into a project cognition graph. ## Core Features & Use Cases - Value-weighted repository inventory: Resolves the candidate scan set through the project-cognition runtime, applies .cognitionignore rules, and classifies every path into P0-P3 value tiers with explicit dispositions. - Subagent-orchestrated deep scanning: Dispatches bounded MapScanPacket lanes to subagents with machine-checkable worker-result handoffs, coverage ledgers, and blocked-state recovery contracts. - Provisional graph artifacts: Emits nodes.json, edges.json, observations.json, coverage.json, and workbench state files under .specify/project-cognition/ for handoff to /sp-map-build. - Use Case: Before running graph-based navigation or planning in a spec-kit project, invoke this Skill to produce a complete evidence baseline so /sp-map-build can reconstruct the cognition graph from live repository surfaces. ## Quick Start Ask the agent to run /sp-map-scan on this repository, optionally naming a subsystem or directory to emphasize, so it produces the project-cognition evidence baseline.

Frequently Asked Questions about sp-map-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a project cognition baseline for a brownfield codebase?▼

Run /sp-map-scan in a spec-kit project with a .specify directory. It resolves the candidate file set through the project-cognition runtime, classifies paths into P0-P3 value tiers, deep-scans high-value files via subagents, and writes provisional graph artifacts under .specify/project-cognition/.

What artifacts does the map scan workflow produce?▼

It writes status.json, an evidence directory, provisional nodes.json, edges.json, and observations.json, coverage.json, plus workbench files such as repository-universe.json, scan-targets.json, scan-queue.json, handoff-ledger.json, and map-state.md. These feed the follow-on /sp-map-build step.

Does sp-map-scan publish the final cognition graph?▼

No. It is explicitly forbidden from publishing final cognition truth or claiming graph readiness. It only produces evidence, provisional structure, and coverage diagnostics; /sp-map-build owns schema v5 graph-store publication, confidence assignment, and alias catalog readiness.

How does .cognitionignore affect which files get scanned?▼

The project-cognition runtime applies root .cognitionignore and .specify/project-cognition/.cognitionignore rules, using gitignore-compatible syntax, to exclude paths from the scan set. If generate-ignore creates a new ignore file, the workflow pauses for user review before inventory continues.

What happens when a scan subagent cannot complete its lane?▼

The workflow records subagent_blocked in status.json, map-state.md, and coverage-ledger.json open gaps, then blocks baseline activation until recovery. Only low-risk P3 or justified P2 paths may become accepted nonblocking gaps with an owner, reason, and revisit condition.