with one click
benshoemaker-us
benshoemaker-us contains 16 collected skills from benjaminshoemaker, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Delegate code implementation to Codex CLI. Claude decomposes, scopes context, and verifies; Codex implements. Accepts a spec file, text description, or gathers requirements interactively.
Exploratory conversation before /product-spec. Asks one question at a time, runs background research for open-source/off-the-shelf alternatives, and writes DISCOVERY_NOTES.md. Use when the user has an idea but hasn't scoped it yet.
Generate EXECUTION_PLAN.md and scoped AGENTS.md files for a feature. Use after /feature-technical-spec to create the task breakdown.
Define feature requirements (problem, users, scope, acceptance criteria) through guided Q&A and write FEATURE_SPEC.md. Use when starting a new feature.
Define technical approach (architecture, integration points, data model) for a feature through guided Q&A and write FEATURE_TECHNICAL_SPEC.md. Use after /feature-spec.
Orient to project structure and load context. Use at the start of each new session or after context reset to understand the project state.
Generate the greenfield execution plan plus root and scoped AGENTS.md files. Use after /technical-spec to create the phased task breakdown.
Resume execution from wherever you left off. Detects current state and runs the appropriate next command, or reports what's blocking progress. Use at the start of any session to pick up where you left off.
Run checkpoint criteria after completing a phase. Use after /phase-start completes all tasks to verify quality gates before proceeding.
Check prerequisites before starting a phase. Use before /phase-start to verify dependencies are met and context is loaded.
Execute all tasks in a phase autonomously. Use after /phase-prep confirms prerequisites are met.
Generate PRODUCT_SPEC.md through guided Q&A. Use as the first step when starting a new greenfield project.
Generate TECHNICAL_SPEC.md through guided Q&A. Use after /product-spec to define the technical architecture.
Capture links, thoughts, and a thesis for a blog post, then research and structure them into a writing brief. Use when starting a new blog post.
Write a blog post draft from a braindump brief, matching Ben's writing voice. Use after /braindump produces a BRIEF.md.
Final quality gate before publishing a blog post. Checks tone/voice match, conciseness, thesis connectivity, evidence backing, structural strength, links, frontmatter, and readability. Use after /draft-post iteration is complete. Replaces /tone-check.