sdlc
25Command
Start (or resume) an autonomous SDLC loop — a state machine on disk driven by a Stop-hook loop (optionally a user-armed /goal), working without questions until DONE or BLOCKED.
Command
Start (or resume) an autonomous SDLC loop — a state machine on disk driven by a Stop-hook loop (optionally a user-armed /goal), working without questions until DONE or BLOCKED.
Hook
Runs when the agent asks permission for an action, executing auto-approve.sh via bash. From JoshuaOliphant/claude-plugins.
Hook
Runs when the agent finishes a response, executing loop-stop-hook.sh via bash. From JoshuaOliphant/claude-plugins.
Hook
Runs when a git worktree is created, executing worktree-create.sh via bash. From JoshuaOliphant/claude-plugins.
Hook
Runs when a git worktree is removed, executing worktree-remove.sh via bash. From JoshuaOliphant/claude-plugins.
Hook
Runs on the StopFailure event, executing stop-failure.sh via bash. From JoshuaOliphant/claude-plugins.
Skill Claude CodeCodex
Use AFTER bdd-spec has produced acceptance criteria, or when the user has existing Given/When/Then scenarios that need pytest-bdd scaffolding. MUST NOT run without existing acceptance criteria — invoke bdd-spec first if none exist. Trigger: "generate feature files", "scaffold BDD tests", "wire up pytest-bdd", "make…
Skill Claude CodeCodex
Use INSTEAD OF superpowers:brainstorming when the user wants structured acceptance criteria in Given/When/Then format. This is the right choice when requirements need to be testable — not just designed. Trigger: "spec this out", "acceptance criteria", "BDD", "behavior driven", "what should happen when", "edge cases"…
Skill Claude CodeCodex
MUST use when creating, updating, or closing Beads issues via bd commands. Use proactively when starting work (bd update --status=inprogress) and completing work (bd close). Trigger: any mention of "issue", "task tracking", "what should I work on", "bd create/ready/close", or when the session hook indicates beads is…
Skill Claude CodeCodex
The autonomous-sdlc state machine. Loaded by every /sdlc loop iteration to decide what one unit of work the current state requires, how to verify it, and which transition to record. Trigger: an active .sdlc/state.json exists, or the /sdlc command invokes it. Not for ad-hoc use outside a loop.
Skill Claude CodeCodex
Python-specific TDD wrapper. Use INSTEAD OF superpowers:test-driven-development when the project uses uv + pytest. Adds: feedback loading from autonomous-sdlc, uv run pytest commands, test directory organization (unit/integration/e2e). Delegates core TDD discipline to superpowers:test-driven-development. Trigger…
Plugin Claude Code
Capture solved problems, retrieve past solutions, and graduate accumulated knowledge into living context. Skills: compound-capture (post-solve documentation), compound-retrieve (pre-work knowledge search), compound-graduate (promote lessons into CLAUDE.md/AGENTS.md).
Agent
Search knowledge/solutions/ for relevant past solutions by YAML frontmatter. Use before implementing features or fixing bugs to surface institutional knowledge and prevent repeated mistakes. Designed for speed (<30s).
Command
Initialize compound knowledge directory structure and optional path configuration.
Skill Claude CodeCodex
Capture this solution NOW — use immediately after solving non-trivial problems, completing debugging sessions, or when the user confirms something works ("that worked", "it's fixed", "finally"). Do NOT wait to be asked — if a debugging session just ended successfully, proactively invoke this. Also trigger on…
Skill Claude CodeCodex
Promote accumulated knowledge into living context. Use when the user says "graduate knowledge", "promote lessons", "update CLAUDE.md from what we've learned", "what should be in my CLAUDE.md", "compound graduate", "improve the system from my notes", or after a run of captures when patterns recur. Scans the read corpus…
Skill Claude CodeCodex
MUST check before starting any debugging session, investigating unfamiliar code, or planning a feature that might have been attempted before. Searches past solutions in knowledge/solutions/ to prevent repeated mistakes. Designed to be fast (<30s). Trigger proactively: before ANY bug investigation, before implementing…
Plugin Claude Code
Build web applications where an AI agent dynamically generates HTML UI using hexagonal/ports-and-adapters architecture with HTMX for interactivity and MCP tools for data operations.
Skill Claude CodeCodex
MUST use when building web apps where an AI agent generates HTML UI dynamically. Use INSTEAD OF superpowers:brainstorming or impeccable:frontend-design when the architecture is agent-driven (Claude Agent SDK + FastAPI + HTMX). Trigger: "build an agent app", "AI-driven web UI", "hexagonal architecture", "ports and…
Plugin Claude Code
Create evidence-based spaced repetition flashcards using cognitive science principles from Andy Matuschak's research. Applies the 5 properties of effective prompts (focused, precise, consistent, tractable, effortful) to create cards that actually work for long-term retention.
Skill Claude CodeCodex
MUST use when the user mentions flashcards, Mochi, spaced repetition, memorization, studying, or wanting to remember something. Trigger proactively when the user says "I want to remember this", "make flashcards", "create Mochi cards", "help me study", "turn this into flashcards", "SRS", "Anki", or "I need to memorize…
Plugin Claude Code
Install a local, Docker-free OTLP observability stack (OpenTelemetry → Vector → JSONL, optionally VictoriaLogs + VictoriaMetrics) into a project and instrument the code, with a scan-and-propose step for domain-appropriate spans and metrics — then query that telemetry as a development feedback signal…
Skill Claude CodeCodex
Install a local, Docker-free OTLP observability stack (OpenTelemetry → Vector → JSONL files, optionally VictoriaLogs + VictoriaMetrics) into a project, and instrument the code to emit traces, metrics, and logs. Use this whenever the user wants observability, telemetry, tracing, metrics, or structured logging in a…
Skill Claude CodeCodex
Query a project's local observability harness (.claude/harness/observability/) as a development feedback signal. Use whenever the project has the harness installed and you are: debugging ("why is this failing", "is this code path even running"), verifying a change actually executed ("did the new endpoint get hit"…