meld-spec-engineering

3

solomonjames

Use when writing acceptance criteria, implementation tasks, or evaluating whether a spec is ready for development — provides Given/When/Then format and ready-for-dev standards

meld-parallel-agents

3

solomonjames

Parallel agent dispatch — when to split work across subagents, how to craft prompts, and how to integrate results. Optional in quick-dev Phase 3.

meld-complexity-assessment

3

solomonjames

Use when a user describes a feature or task to determine the right depth of planning — routes to direct execution, quick-spec, or full MELD flow based on complexity signals

meld-personas

3

solomonjames

Use when you need an expert perspective for a specific phase of product development — provides 8 specialist personas with distinct communication styles and expertise areas

meld-quick-dev

3

solomonjames

Use when ready to implement a feature — 7-phase implementation flow with mode detection, execution, code simplification, self-check, adversarial review, and finding resolution

using-meld

3

solomonjames

Use when starting any conversation - establishes when to use MELD methodology skills for structured product development, spec engineering, and adversarial review

meld-artifact-templates

3

solomonjames

Use when you need a structured output template for MELD workflow artifacts — provides templates for tech specs, stories, PRDs, architecture decisions, and more

meld-adversarial-review

3

solomonjames

Use when implementation is complete and you need a code review with information asymmetry — reviewer sees ONLY the diff, not the spec or conversation history

meld-debugging

3

solomonjames

Systematic debugging — 4-phase root cause methodology with mandatory investigation before any fix. Referenced by quick-dev halt conditions.

meld-tdd

3

solomonjames

Test-driven development methodology — write the test first, watch it fail, write minimal code to pass. Referenced by quick-dev Phase 3.

meld-quick-spec

3

solomonjames

Use when a feature needs a spec before coding — conversational spec engineering that produces a ready-for-dev tech spec through understand, investigate, generate, and review phases

meld-verification

3

solomonjames

Verification before completion — 5-step gate function that requires fresh evidence for every completion claim. Referenced by quick-dev Phases 5 and 7.

meld-worktrees

3

solomonjames

Git worktree creation with ticket-based branch naming — isolate work in a separate directory with automatic setup and lifecycle management. Referenced by quick-dev Phase 1 and 6.

meld-code-simplifier

3

solomonjames

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Used as a subagent pass on modified code before self-check and adversarial review.