A comprehension-first workflow for Claude Code: grill the problem, design on paper, build one commit at a time, verify against a running app, then write only the tests that earn their place.
Skill Claude CodeCodex
Implement a solution write-up (typically the markdown file produced by /solve-me) in this Laravel project, following existing project patterns and Laravel best practices. Cuts the work into commits itself, writes the commit plan to docs/build/ .md, and gets the developer's approval before writing any code. Then builds…
Skill Claude CodeCodex
Ruthlessly eliminate comprehension debt before design or implementation. Use when the developer wants to stress-test a plan, decision, requirement, bug, feature, architecture, or implementation idea. The developer must demonstrate that they understand the problem, constraints, behavior, and consequences in their own…
Skill Claude CodeCodex
Build the comprehension map across every ship-me run in this project and read it back in plain language. Runs a deterministic script over the markdown the pipeline already wrote (grill-me's R-numbers, solve-me's sub-problems and options, build-me's commits and touched files, verify-me's coverage table) and turns them…
Skill Claude CodeCodex
Run the full pipeline end to end for one problem or feature: /grill-me, /solve-me, /build-me, /verify-me, /test-me, in order. The interactive phases (grill-me's interrogation, build-me's per-commit review) run right here in this conversation. The non-interactive phases (solve-me, verify-me, test-me) each run as a…
Skill Claude CodeCodex
Turn an understood problem into a solution, using divide-and-conquer. Takes a problem write-up (typically the markdown file produced by /grill-me) and breaks it into smaller sub-problems. For each sub-problem, proposes every genuinely different solution that actually exists — three or more where there's real design…
Skill Claude CodeCodex
Write the automated unit and feature tests that /verify-me identified as missing, following this project's testing conventions and real testing best practices. Actively filters out useless tests — ones that can't fail, test the framework instead of the feature, or lock in implementation details instead of behavior.…
Skill Claude CodeCodex
Check that a built feature actually matches the original problem (/grill-me) and the chosen solution (/solve-me). Acts like a real user and a QA engineer, not a code reviewer: confirms scope, environment, database safety and login with the developer first, then creates real dummy data in the database (via Laravel…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: