Agent Claude Code
Implements ONE numbered task from a feature's tasks.md, following the project's constitution and stack rules. Use AFTER planner produced tasks.md and researcher produced research.md. The orchestrator specifies which task number. Writes code + colocated tests. Stack-agnostic.
Agent Claude Code
Breaks a feature spec + design into atomic, ordered, testable tasks. Use AFTER spec.md and design.md exist and AFTER the researcher's report. Writes specs/ /tasks.md. Stack-agnostic.
Agent Claude Code
Read-only codebase explorer for Spec-Driven Development. Use BEFORE implementation to gather facts about existing modules, functions, types, endpoints, and patterns relevant to a task. Returns a structured findings report with file:line citations. NEVER edits files. Stack-agnostic.
Agent Claude Code
Reviews the diff against the task's acceptance criteria, the spec, the constitution, and the stack rules. Use AFTER the tester reports green and the verifier returns PASS. Returns approve / request-changes with cited issues. Read-only. Stack-agnostic.
Agent Claude Code
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
Agent Claude Code
The loop's verifier. Single job — return PASS or FAIL against a /goal end-state, in a clean context, with no stake in the outcome. Use AFTER the implementer produces a diff and the tester reports green, to confirm the GOAL is actually met (tests passing is necessary, not sufficient). Read-only on source; runs…
Command Claude Code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
Command Claude Code
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.
Command Claude Code
Command "build" from chohra-med/expo_boilerplate, covering command: build — run the sdd pipeline over tasks.md, invocation, per-task cycle, gates (constitution) and output.
Command Claude Code
Command "generate-agents" from chohra-med/expo_boilerplate, covering invocation, how it works, the concern each agent gets (one per agent), rules for the injected block (every agent) and idempotent + the loop.
Command Claude Code
Command "init" from chohra-med/expo_boilerplate, covering command: init — spec-driven bootstrap, invocation, step 1 — capture intent (the interview, one message), step 2 — scaffold (copy from templates/, fill the {{...}}) and step 4 — write the first spec from the goal.
Command Claude Code
Command "learn" from chohra-med/expo_boilerplate, covering command: learn — the learning loop (feedback → rules), when to run it, invocation, the loop (6 steps) and 1 — capture.
Command Claude Code
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
Command Claude Code
Command "plan" from chohra-med/expo_boilerplate, covering command: plan — spec → design (the how), invocation, the design must contain and rule.
Command Claude Code
Command "rules" from chohra-med/expo_boilerplate, covering invocation, what a "rules-boundary" directory is, the five sections (one owner agent each), generate (the "create them if they don't exist" path) and resolve (what each agent reads).
Command Claude Code
Command "spec" from chohra-med/expo_boilerplate, covering command: spec — brief → structured spec (the what), invocation, the spec must contain and rules.
Command Claude Code
Command "tasks" from chohra-med/expo_boilerplate, covering command: tasks — design → atomic task list, invocation, each task and standard ordering (drop what's irrelevant).
Command Claude Code
Command "tickets" from chohra-med/expo_boilerplate, covering invocation, source a — a ticket mcp (linear / github issues / jira / …), source b — an inline plan (no ticket system), then: build and hard rules.
Command Claude Code
Command "verify" from chohra-med/expo_boilerplate, covering command: verify — run the verifier alone, invocation, what it does and why a separate command.
Skill Claude CodeCodex
Health-check the memory bank, rules, and index — flag stale, contradictory, or redundant entries and spec↔code drift. Use when Malik says 'audit the bank', 'is the memory stale', 'check spec harness health', or 'clean up the rules'.
Skill Claude CodeCodex
Run the SDD pipeline over tasks.md: implement → test → VERIFY → review, one task at a time, under the ratchet. Use when Malik says 'build it', 'run the pipeline', 'implement the tasks', or 'ship this feature'. Each task gated by the separate verifier; lessons harvested by learn.
Skill Claude CodeCodex
Bind the 6 SDD agents to THIS project's rules — fill each agent's GEN:rules region with its concern's real rules (implementer←Coding, tester←Testing+commands, reviewer←Reviewing, researcher/planner←Architecture, verifier←goal). Use when Malik says 'generate the agents', 'make the agents project-specific', 'bind agents…
Skill Claude CodeCodex
Add or refresh Spec Harness in a repo — greenfield (new) or existing (integrate), idempotent. Use when Malik says 'install spec harness', 'set this repo up with spec harness', 'integrate spec harness into X', or 'start a new spec-harness project'. Runs the interview (mode, stack, constraints, work-intake source…
Skill Claude CodeCodex
The learning loop — turn feedback, a correction, or a verifier-FAIL root cause into one enforced rule injected into the ratchet (AGENTS.md/airules), dated. Use when Malik says 'learn this', 'remember not to do X', 'capture this lesson', 'don't do that again', or right after he corrects you. Closes the loop the…