skill-init

Skill-Init — Project Bootstrap

Run this skill exactly once per project, before any other super-skill. It creates the infrastructure all other skills depend on.

Announce: "I'm using skill-init to set up the super-skills project structure."

# Environment check (auto-injected):
!echo "git:     $(git --version 2>/dev/null || echo 'NOT FOUND')"
!echo "python3: $(python3 --version 2>/dev/null || echo 'NOT FOUND')"
!echo "gh:      $(gh --version 2>/dev/null | head -1 || echo 'NOT FOUND')"
!echo "shell:   $SHELL"

---

Step 1: Validate Environment

# Check git
git rev-parse --git-dir 2>/dev/null && echo "GIT: OK" || echo "GIT: MISSING"

# Check we're in a repo root (not a subdirectory)
git rev-parse --show-toplevel

# Check write access
touch docs/.skill-init-test 2>/dev/null && rm docs/.skill-init-test \
  && echo "WRITE: OK" || echo "WRITE: FAILED — check permissions"

If GIT: MISSING → stop. Super-skills requires git. Initialize with git init first. If WRITE: FAILED → stop. Fix permissions before proceeding.

Harness Capability Check

# Check if subagent dispatch (Task tool) is available
# This determines whether specialist-review's subagent path works
echo "HARNESS: $(basename $SHELL) / check Task tool manually in your agent UI"

Note the following limitations by environment:

Environment	Task tool (subagents)	[E.IJ] via Artifacts
Claude Code CLI	✅ supported	❌ no artifact runtime — use subagent fallback
claude.ai chat	❌ not available	✅ Artifacts API works
Cursor / Codex	✅ supported	❌ no artifact runtime — use subagent fallback
OpenCode	✅ supported	❌ no artifact runtime — use subagent fallback

Record which environment this project uses — affects specialist-review behavior.

---

Step 1b: DPS Misplacement Scan — Safe Mode

Before creating new directories, ensure the project doesn't already have a DPS structure hidden in a non-standard path.

Default behavior is DRY-RUN. Do not move or delete any existing DPS directory unless the user explicitly confirms or APPLY=true is set.