Run any Skill in Manus with one click

sprang-onboard

Stars1

Forks1

UpdatedJune 8, 2026 at 04:57

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".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

FavioVazquez

FavioVazquez/sprang

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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".

Ensure .sprang/knowledge-graph.json exists with phase: complete. If not, run /sprang-analyze first.
Call sprang_health to summarize total nodes, edges, top risk areas, and smell counts.
Ask about persona (or infer from context). Supported personas:
- non-technical — executive / business stakeholder → entry-points and domain nodes only, no code details
- pm — product manager → domain and service nodes focused on business capabilities
- junior — developer new to this codebase → all steps with language lessons (default)
- senior or experienced — experienced engineer → skip intro, focus on risks, decisions, and coupling
Call sprang_tour with the matching persona string (non-technical, pm, junior, or senior) to load the guided tour. Present each step with its explanation.
For any tour node with risk_score > 0.6, call sprang_why to surface decision context and any team annotations.
Call sprang_node on the top 3 highest-risk tour nodes to show layer membership, in/out degree, and annotation status.
Call sprang_domain to list all business domains and explain how code maps to real-world processes.
Highlight the top 3 highest-risk nodes the newcomer must be aware of before making changes.
Recommend:
- Read .sprang/SPRANG_REPORT.md for the full architectural summary
- Run /sprang-diff before submitting any PR
- Open the dashboard (pnpm --filter @sprang/dashboard dev) and switch to the Learn tab for the interactive persona-adaptive tour
- Run /sprang-team to see any existing team annotations

More from this repository

same repository

sprang-analyze

FavioVazquez/sprang

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".

2026-06-171

sprang

FavioVazquez/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".

2026-06-171

sprang-team

FavioVazquez/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".

2026-06-081

sprang-health

FavioVazquez/sprang

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".

2026-06-081

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".

Ensure .sprang/knowledge-graph.json exists with phase: complete. If not, run /sprang-analyze first.
Call sprang_health to summarize total nodes, edges, top risk areas, and smell counts.
Ask about persona (or infer from context). Supported personas:
- non-technical — executive / business stakeholder → entry-points and domain nodes only, no code details
- pm — product manager → domain and service nodes focused on business capabilities
- junior — developer new to this codebase → all steps with language lessons (default)
- senior or experienced — experienced engineer → skip intro, focus on risks, decisions, and coupling
Call sprang_tour with the matching persona string (non-technical, pm, junior, or senior) to load the guided tour. Present each step with its explanation.
For any tour node with risk_score > 0.6, call sprang_why to surface decision context and any team annotations.
Call sprang_node on the top 3 highest-risk tour nodes to show layer membership, in/out degree, and annotation status.
Call sprang_domain to list all business domains and explain how code maps to real-world processes.
Highlight the top 3 highest-risk nodes the newcomer must be aware of before making changes.
Recommend:
- Read .sprang/SPRANG_REPORT.md for the full architectural summary
- Run /sprang-diff before submitting any PR
- Open the dashboard (pnpm --filter @sprang/dashboard dev) and switch to the Learn tab for the interactive persona-adaptive tour
- Run /sprang-team to see any existing team annotations