leadership-build
Structure a team's roles, ownership areas, RAPID decision rights, per-person delegation levels and collaboration norms. Use when the user's team has unclear ownership, duplicated work or everything es
SKILL.mdskills/leadership-build/SKILL.md
GitHubBuild
Structure the team for "$ARGUMENTS". Define roles, responsibilities, ownership areas, and establish a delegation framework.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"leadership-build","workflow":"leadership","phase":3,"project":"<project>","event":"skipped","artifact":"03-build.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 3 (Build) of the Leadership Development workflow (leadership); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or leadership when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"leadership-build","workflow":"leadership","phase":3,"project":"<project>","event":"refused","artifact":"03-build.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"leadership-build","workflow":"leadership","phase":3,"project":"<project>","event":"started","artifact":"03-build.md","note":""}.
Read .singularskills/leadership/<project>/01-assess.md and .singularskills/leadership/<project>/02-vision.md. If 02-vision.md does not exist, tell the user:
Phase 2 (Vision) has not been completed for "<project>". Run
/leadership-vision <project>first, or use--skip-checksto bypass.
Process
Read context:
- Read
.singularskills/leadership/<project>/01-assess.mdfor team assessment - Read
.singularskills/leadership/<project>/02-vision.mdfor values and culture - Read
references/decision-frameworks.md
- Read
Define team structure:
- Map each team member's role and primary responsibilities
- Identify ownership areas — who owns what?
- Clarify decision rights using the RAPID framework
- Identify gaps: any roles or skills missing?
Create delegation framework:
- For each team member: what can they own autonomously?
- What needs consultation before deciding?
- What do you retain as leader?
- Match delegation level to team member maturity (from Assess)
Define collaboration norms:
- How does work get assigned and tracked?
- What's the escalation path for blockers?
- How do team members collaborate across ownership areas?
Write the artifact to
.singularskills/leadership/<project>/03-build.mdwith sections:- Team Structure — roles, responsibilities, ownership map
- Decision Rights — RAPID matrix for key decision types
- Delegation Framework — per-person autonomy levels
- Collaboration Norms — assignment, tracking, escalation
Output
The team structure written to .singularskills/leadership/<project>/03-build.md. Present a summary highlighting:
- Ownership map
- Key delegation decisions
- Any gaps identified
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"leadership-build","workflow":"leadership","phase":3,"project":"<project>","event":"finished","artifact":"03-build.md","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: leadership-build
workflow: leadership
phase: 3
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>