원클릭으로 Manus에서 모든 스킬 실행

sprang-team

스타1

포크1

업데이트2026년 6월 4일 08:48

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

FavioVazquez

FavioVazquez/sprang

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

SKILL.md

readonly

name	sprang-team
description	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".

Browse and write team annotations attached to graph nodes.

Arguments: [node path or ID] (optional)

Check .sprang/knowledge-graph.json exists — if not, run /sprang-analyze first.
List all files in .sprang/annotations/ to find every annotated node.
For each annotation file, read YAML frontmatter: node_id, node_label, annotated_at, tags.
If no annotations exist: suggest candidates using step 8 below, then offer to write the first one.
Present annotation index table sorted by annotated_at descending.
If argument is a node path or ID: call sprang_why + sprang_node for that node and display annotation, decision context, and current structural state side-by-side.
Staleness detection — for each annotated node:
- Call sprang_node to get node.decision_context.last_changed and current in_degree/out_degree
- If last_changed > annotated_at: flag as ⚠️ possibly stale
- Report a staleness summary table
Suggest unannotated candidates: nodes with risk_score > 0.6 OR in_degree > 10 that have no annotation file.
Offer to write: use sprang_annotate MCP tool to create .sprang/annotations/<node-id>.md with purpose, decisions, caveats, and ownership.

$ARGUMENTS

이 저장소의 다른 Skills

같은 저장소

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-onboard

FavioVazquez/sprang

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

name	sprang-team
description	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".

Browse and write team annotations attached to graph nodes.

Arguments: [node path or ID] (optional)

Check .sprang/knowledge-graph.json exists — if not, run /sprang-analyze first.
List all files in .sprang/annotations/ to find every annotated node.
For each annotation file, read YAML frontmatter: node_id, node_label, annotated_at, tags.
If no annotations exist: suggest candidates using step 8 below, then offer to write the first one.
Present annotation index table sorted by annotated_at descending.
If argument is a node path or ID: call sprang_why + sprang_node for that node and display annotation, decision context, and current structural state side-by-side.
Staleness detection — for each annotated node:
- Call sprang_node to get node.decision_context.last_changed and current in_degree/out_degree
- If last_changed > annotated_at: flag as ⚠️ possibly stale
- Report a staleness summary table
Suggest unannotated candidates: nodes with risk_score > 0.6 OR in_degree > 10 that have no annotation file.
Offer to write: use sprang_annotate MCP tool to create .sprang/annotations/<node-id>.md with purpose, decisions, caveats, and ownership.

$ARGUMENTS