メニュー
Guided architecture tour for new team members — adapts to junior, senior, or PM persona. Use when the user says "/sprang-onboard", "onboard me", "give me a tour", "I'm new to this codebase", or "walk me through the architecture".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Analyze a codebase to produce a rich semantic knowledge graph — file summaries, architecture layers, guided tour, domain map, risk scores. Use when the user says "/sprang-analyze", "analyze the codebase", "full analysis", or "run sprang-analyze".
Analyze a codebase to produce a rich semantic knowledge graph — file summaries, architecture layers, guided tour, domain map, risk scores. Use when the user says "/sprang-analyze", "analyze the codebase", "full analysis", or "run sprang-analyze".
Build or refresh the Sprang knowledge graph for this workspace. Use when the user says "/sprang", "build the knowledge graph", "scan the codebase", "index this project", or "run sprang".
Build or refresh the Sprang knowledge graph for this workspace. Use when the user says "/sprang", "build the knowledge graph", "scan the codebase", "index this project", or "run sprang".
Browse and write team annotations attached to graph nodes — institutional knowledge, decision history, ownership. Use when the user says "/sprang-team", "add annotation", "team knowledge", "who owns this", or "document this decision".
Full structural health report — health grade, code smells, security issues, risk nodes, orphans, circular dependencies. Use when the user says "/sprang-health", "health report", "code smells", "show risks", "what's broken", "security issues", or "architectural health".
| name | sprang-onboard |
| description | Guided architecture tour for new team members — adapts to junior, senior, or PM persona. Use when the user says "/sprang-onboard", "onboard me", "give me a tour", "I'm new to this codebase", or "walk me through the architecture". |
.sprang/knowledge-graph.json exists with phase: complete. If not, run /sprang-analyze first.sprang_health to summarize total nodes, edges, top risk areas, and smell counts.non-technical — executive / business stakeholder → entry-points and domain nodes only, no code detailspm — product manager → domain and service nodes focused on business capabilitiesjunior — developer new to this codebase → all steps with language lessons (default)senior or experienced — experienced engineer → skip intro, focus on risks, decisions, and couplingsprang_tour with the matching persona string (non-technical, pm, junior, or senior) to load the guided tour. Present each step with its explanation.risk_score > 0.6, call sprang_why to surface decision context and any team annotations.sprang_node on the top 3 highest-risk tour nodes to show layer membership, in/out degree, and annotation status.sprang_domain to list all business domains and explain how code maps to real-world processes..sprang/SPRANG_REPORT.md for the full architectural summary/sprang-diff before submitting any PRpnpm --filter @sprang/dashboard dev) and switch to the Learn tab for the interactive persona-adaptive tour/sprang-team to see any existing team annotations