sp-map-update

Incrementally refresh a query-backed project cognition baseline from git diffs and user corrections.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a project cognition baseline accurate after code changes normally requires a full rebuild, which is slow and discards useful existing knowledge. This Skill updates only the affected runtime records in the SQLite-backed cognition store using diff-driven evidence or explicit user corrections. ## Core Features & Use Cases - Incremental Cognition Updates: Computes impact closure from git changes, refreshes affected evidence, claims, and conflicts, and patches only the touched records in .specify/project-cognition/project-cognition.db. - Claim Lifecycle Management: Invalidates affected graph claims as stale with auditable transitions and reconciles them only through claim-specific bounded evidence via claim-reconcile. - Guarded Escalation: Reserves full rebuilds for missing baselines, schema failures, or invalid baseline identity, recording partial refreshes, known unknowns, and minimal live reads otherwise. - Use Case: After renaming a service module and editing its consumers, run this Skill to update ownership, routing aliases, and verification routes in the cognition runtime without rebuilding the entire project map. ## Quick Start Ask the agent to run /sp-map-update for the changed paths in src/services to refresh the project cognition baseline incrementally.

Frequently Asked Questions about sp-map-update

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

FAQPage Schema
How do I update a project cognition baseline without a full rebuild?▼

Run sp-map-update with the changed paths or commit range. It computes the affected closure from git changes, patches only the impacted records in project-cognition.db, and re-validates readiness instead of rebuilding the whole baseline.

When should I use sp-map-update instead of sp-map-scan and sp-map-build?▼

Use sp-map-update whenever a usable baseline exists and changes are incremental. Full rebuild via sp-map-scan then sp-map-build is reserved for missing baselines, schema failures, explicit rebuild requests, or architecture changes that invalidate baseline identity.

What inputs does sp-map-update require?▼

It requires a spec-kit project structure with a .specify directory, the status.json and project-cognition.db runtime files, and either changed paths, a commit range, or user-supplied corrections describing what changed.

What happens if the update cannot fully prove the affected closure?▼

It still updates the records that can be proven and records the rest as partial_refresh, low-confidence claims, conflicts, known unknowns, and minimal live reads. Ordinary uncertainty never triggers a silent full rebuild.

How are stale graph claims reconciled after an update?▼

Affected claims are marked stale with their stable IDs returned in affected_graph_claims. Re-promotion requires claim-specific bounded live evidence submitted through project-cognition claim-reconcile prepare, then executing the returned apply_argv exactly.