From solid-coder
Orchestrate implementation of a spec, reads the spec, finds dependencies, plans architecture, validates plan with the current codebase, synthesize implementation plan, write code, does validation of the implementation with checkpoint asking user validation, does on round of refactoring for self-validation TRIGGER when: user says "implement spec", "implement" and passes spec file
How this skill is triggered — by the user, by Claude, or both
Slash command
/solid-coder:implement <spec-file-path> [--verbose] [--iterations N]<spec-file-path> [--verbose] [--iterations N]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Accepts a feature spec file and coordinates sub-skills to architect, validate, synthesize, implement, and review the feature — all in one command.
Accepts a feature spec file and coordinates sub-skills to architect, validate, synthesize, implement, and review the feature — all in one command.
~/.solid-coder/{project-slug}/implement-{spec-number}-<YYYYMMDDhhmmss> (computed via MCP tool)number field)implement-log.json output. Default: off./build-spec to create one."
--verbose is present, false otherwise--iterations N is present, 1 otherwise.md. If not, fail with the same message as 0.1.mcp__plugin_solid-coder_specs__parse_spec with the spec file path. On error, stop and report the message.date -u +%Y%m%d-%H%M%Smcp__plugin_solid-coder_pipeline__get_output_path with {operation: "implement", spec_number: "{number}"} → store result as OUTPUT_ROOT{OUTPUT_ROOT}/spec.mdresources/ directory exists as a sibling of the spec file. If yes, copy it to {OUTPUT_ROOT}/resources/ (preserving all files — screenshots, schemas, etc.)implement-log.json at {OUTPUT_ROOT}/implement-log.json with empty phases arraysolid-coder:plan-agentspec: {OUTPUT_ROOT}/spec.md
output: {OUTPUT_ROOT}/arch.json
implement-log.json with { "phase": "plan", "status": "success" }/plan manually to debug." STOP.solid-coder:validate-plan-agentarch-json: {OUTPUT_ROOT}/arch.json
output: {OUTPUT_ROOT}/validation.json
implement-log.json with { "phase": "validate-plan", "status": "success" }/validate-plan manually to debug." STOP.solid-coder:synthesize-implementation-agentarch-json: {OUTPUT_ROOT}/arch.json
validation-json: {OUTPUT_ROOT}/validation.json
output: {OUTPUT_ROOT}/implementation-plan.json
implement-log.json with { "phase": "synthesize-implementation", "status": "success" }/synthesize-implementation manually to debug." STOP.{OUTPUT_ROOT}/implementation-plan.json → extract matched_tags[] as comma-separated string. Store as MATCHED_TAGS. If empty or missing, set MATCHED_TAGS to empty string.solid-coder:code-agentmode: implement
plan: {OUTPUT_ROOT}/implementation-plan/
matched-tags: {MATCHED_TAGS}
implement-log.json with { "phase": "code", "status": "success" }SKIP THIS STEP MOVE TO PHASE 6
{OUTPUT_ROOT}status == "skipped" or "approved" → proceed to Phase 6status == "has_fixes":
solid-coder:code-agentmode: implement
plan: {fixes_path}
implement-log.json with { "phase": "validate-implementation", "status": "success" }git add -A to capture all changeschanges --iterations {ITERATIONS} (if VERBOSE: append --verbose)implement-log.json with { "phase": "refactor", "status": "success" }implement-log.json with all phase entries/implement complete
Spec: {spec file}
Run: {OUTPUT_ROOT}
Phases: plan ✓ | codebase ✓ | synthesize ✓ | code ✓ | validate ✓ | review ✓
(Mark failed/skipped phases accordingly)--iterations N is set with N > 0.run_in_background: true) — background agents hit permission prompts silently and stall.npx claudepluginhub swift-gurus/solid-coderCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.