Skip to main content
skill CX Codex

implementation-approach · shinpr/claude-code-workflows — Claude Code skill for strategy selection

implementation-approach — a Claude Code skill for choosing an implementation strategy and verification criteria. It activates during planning and when comparing development approaches.

MIT ★ 720 updated 2026-11-11

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add shinpr/claude-code-workflows --skill implementation-approach -a claude-code
Open on GitHub

What implementation-approach does

The skill examines the current implementation, project requirements, and verified constraints to help select a delivery path. It starts from the simplest route through existing responsibilities. Proposed additions stay only when removing them would break a requirement, a required boundary, or necessary proof.

The comparison considers overall complexity, dependencies, risks, and verification boundaries. If an unknown fact blocks the next step, the skill turns it into a specific evidence prerequisite. The result is a selected design with reasons for each added part; an implementer can apply the same checks without creating a separate document.

Install it for Claude Code with npx skills add shinpr/claude-code-workflows --skill implementation-approach -a claude-code. The skill file is at ~/.claude/skills/implementation-approach/SKILL.md.

What it helps with

  • compare implementation options by total complexity
  • test a plan against project requirements and constraints
  • remove additions that are not needed to meet the outcome
  • identify evidence needed before moving to the next step

Example prompts for the agent

  • Compare implementation paths for this feature and choose the simplest one that meets the requirements.
  • Review the current architecture and define verification criteria for this change.
  • Assess this migration plan for risks and constraints that could affect the strategy.

How to install implementation-approach

1Skills CLI (Vercel)

npx skills add shinpr/claude-code-workflows --skill implementation-approach -a claude-code

2Manually: put the files in place

~/.claude/skills/implementation-approach/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/implementation-approach/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about implementation-approach

How do I install implementation-approach in Claude Code?

Run npx skills add shinpr/claude-code-workflows --skill implementation-approach -a claude-code. The skill file is placed at ~/.claude/skills/implementation-approach/SKILL.md.

What does implementation-approach do?

It helps select an implementation strategy by examining the current code, requirements, and constraints, then comparing viable options by their total complexity.

When does implementation-approach activate?

Use it while planning an implementation, choosing a development approach, or setting verification criteria.

Source text

SKILL.md · MIT
---
name: implementation-approach
description: Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
---

# Implementation Strategy Selection Framework (Meta-cognitive Approach)

## Meta-cognitive Strategy Selection Process

### Phase 1: Decision-Sufficient Current State Analysis

**Core Question**: "What does the existing implementation look like?"

#### Analysis Framework
```yaml
Architecture Analysis: Responsibility separation, data flow, dependencies, technical debt
Implementation Quality Assessment: Code quality, behavior-relevant test evidence, performance, security
Historical Context Understanding: Current form rationale, past decision validity, constraint changes, requirement evolution
```

#### Meta-cognitive Question List
- What is the true responsibility of this implementation?
- Which parts are business essence and which derive from technical constraints?
- What dependencies or implicit preconditions are unclear from the code?
- What benefits and constraints does the current design bring?

Stop when the current-state facts that could change responsibility, reuse, option validity, total complexity, a contract, or verification have been checked; find existing code as coding-principles Reference Representativeness describes.

### Phase 2: Design Convergence

Complete these steps in order before selecting an implementation strategy:

1. **Existing-Surface Baseline**: Form the simplest end-to-end path that delivers the current outcome through existing responsibilities. Explicit requirements and accepted decisions are binding; suggested mechanisms remain candidates.
2. **Evidence Check**: Test that path against current requirements, verified constraints, observed in-scope problems, and evidence-backed material risks. Keep only the unmet conditions that can change the selected design. Where the requirements leave a quality level unset, such as performance, freshness, consistency, availability, or protection beyond the required trust boundary, test against the lowest level that still delivers the outcome and record it as the selected level.
3. **Targeted Comparison**: For each unmet condition, test reuse, derivation from existing data, on-demand computation, or responsibility at the current caller or boundary before adding design surface. Compare viable choices by total complexity across the dimensions that materially differ: user decisions, settings, modes, concepts, outputs, persistent state, implementation paths, UX, runtime, implementation, testing, documentation, and maintenance. A second implementation of a responsibility that already has an owner with the same contract and change reason, including one added earlier in the same change, adds design surface; reusing or relocating that owner removes it. Select the lowest-total-complexity choice that satisfies the condition.
4. **Subtraction Check**: Remove each proposed addition and re-test its governing condition. Retain it only when the outcome, a required boundary, or necessary proof becomes unmet at its origin (a requirement, an accepted decision, or a repository rule or contract); a criterion, invariant, or constraint that a workflow artifact derived from that origin is narrowed to what the origin requires instead.

Classify supporting claims as observed, inferred, or unknown. Route an unknown that blocks the next step as an exact evidence prerequisite; the caller's value-boundary and irreversible-action gates determine whether user interaction is required.

Candidate paths and rejected additions remain active analysis. The durable output is the **Selected Design**: the complete chosen path plus evidence for each added design surface and the condition that fails when it is removed. An accepted ADR may retain alternatives as decision history. An implementer uses the same convergence check without producing a separate artifact.

### Phase 3: Strategy Exploration and Creation

**Core Question**: "When determining before → after, what implementation patterns or strategies should be referenced?"

#### Strategy Discovery Process
```yaml
Direct Strategy: Smallest repository-supported change that satisfies the accepted requirements and constraints
Repository Alternatives: Existing patterns that materially differ in migration, dependency order, or verification boundary
External Research: Official/current sources only when repository evidence cannot resolve a time-sensitive capability, compatibility, or dependency decision
```

#### Reference Strategy Patterns

**Legacy Handling Strategies**:
- Strangler Pattern: Gradual migration through phased replacement
- Facade Pattern: Complexity hiding through unified interface
- Adapter Pattern: Bridge with existing systems

**New Development Strategies**:
- Feature-driven Development: Vertical implementation prioritizing user value
- Foundation-driven Development: Foundation-first construction prioritizing stability
- Risk-driven Development: Prioritize addressing maximum risk elements

**Integration/Migration Strategies**:
- Proxy Pattern: Transparent feature extension
- Decorator Pattern: Phased enhancement of existing features
- Bridge Pattern: Flexibility through abstraction

Use these patterns only when their named migration or dependency problem exists. Start with the direct strategy. Compare an alternative when it would materially change risk, rollout, compatibility, or the early verification point. Keep the option set limited to patterns that produce one of those material differences.

### Phase 4: Material Risk Assessment and Control

**Core Question**: "What risks arise when applying this to existing implementation, and what's the best way to control them?"

Evaluate only risk categories for which current evidence can change the strategy, public contract, rollout, rollback, or verification boundary.

#### Conditional Risk Categories
```yaml
Technical Risks: System impact, data consistency, performance degradation, integration complexity
Operational Risks: Service availability, deployment downtime, process changes, rollback procedures
```

### Phase 5: Decision-Relevant Constraint Compatibility

**Core Question**: "What are this project's constraints?"

Check only constraints evidenced by the governing requirements, repository, external contracts, or current environment that can change the selected strategy or verification boundary.

#### Conditional Constraint Categories
```yaml
Technical Constraints: Library compatibility, resource capacity, mandatory requirements, numerical targets
Temporal Constraints: Deadlines/priorities, dependencies, milestones, learning periods
```

### Phase 6: Implementation Approach Decision

Select the implementation approach that directly fits the verified dependency and delivery constraints:

#### Vertical Slice (Feature-driven)
**Characteristics**: Vertical implementation across all layers by feature unit
**Application Conditions**: Default when an end-to-end value unit can be delivered and verified independently. Data-model sharing and layer breadth are supporting evidence, not substitutes for independent deliverability
**Verification Method**: End-user value delivery at each feature completion

#### Horizontal Slice (Foundation-driven)
**Characteristics**: Phased construction by architecture layer
**Application Conditions**: Use when a common foundation blocks consumer work or must pass stability/compatibility verification before dependent slices can proceed. Materially shared dependency ownership across multiple consumers is a signal to evaluate this approach
**Verification Method**: Integrated operation verification when all foundation layers complete

#### Hybrid
**Characteristics**: Flexible combination according to project characteristics
**Application Conditions**: Use when a verified foundation step is required first and later work can proceed as independently verifiable value slices. Resolve blocking requirement ambiguity before selecting the implementation approach
**Verification Method**: Verify at appropriate L1/L2/L3 levels according to each phase's goals

### Phase 7: Decision Rationale Documentation

Record in the applicable implementation or design decision record:
1. Selected strategy name and characteristics
2. Current evidence and total-complexity basis for added design surface
3. Controls for each material risk activated in Phase 4
4. Compatibility with each decision-relevant constraint activated in Phase 5
5. Verification level (L1/L2/L3) and integration point definition

Alternatives remain active analysis unless an accepted ADR owns them as decision history.

## Verification Level Definitions

Priority for completion verification of each task:

- **L1: Functional Operation Verification** - Operates as end-user feature (e.g., search executable)
- **L2: Test Operation Verification** - Tests that prove the changed behavior pass
- **L3: Build Success Verification** - Code builds/runs without errors

**Priority**: L1 > L2 > L3 in order of verifiability importance

## Integration Point Definitions

Define integration points according to selected strategy:
- **Strangler-based**: When switching between old and new systems for each feature
- **Feature-driven**: When users can actually use the feature
- **Foundation-driven**: When all architecture layers are ready and E2E tests pass
- **Hybrid**: When individual goals defined for each phase are achieved

## Quality Checks

1. Confirm Phase 1 identifies the current responsibility, dependency path, and historical constraints before selecting a strategy
2. Confirm Phase 2 produces one complete Selected Design and every added design surface maps to current evidence, lower-surface insufficiency, and a failed condition under subtraction
3. Confirm Phase 4 records concrete controls for every evidenced material risk; no entry is required for an inapplicable category
4. Confirm Phase 5 checks every evidenced constraint that can change strategy selection or verification; no entry is required for an inapplicable category
5. Confirm Phase 7 records the selected strategy, its total-complexity basis, and the early verification point; alternatives appear only in an accepted ADR

## Guidelines for Meta-cognitive Execution

1. **Leverage Known Patterns**: Use a pattern when its problem and trade-off match the observed repository state
2. **Conditional External Research**: Use official/current sources when a time-sensitive capability, compatibility, or dependency decision remains unresolved after repository inspection
3. **Apply 5 Whys**: Pursue root causes to grasp essence
4. **Multi-perspective Evaluation**: Evaluate current state, convergence, risk, and constraints before selecting the implementation approach

© shinpr · MIT · shinpr/claude-code-workflows

Similar skills

All skills for Agent setup: memory, context, orchestration →

implementation-approach by other authors comes first.

implementation-approach shinpr The implementation-approach Claude Code skill helps choose an implementation strategy and assess its risks. It comes into play when planning a feature against an existing codebase. CX Codex +1 1installs 10x-implement przeprogramowani 10x-implement — a command to implement approved technical plans step-by-step in Claude Code. Reads the plan, tracks progress, and verifies each phase before moving on. CX Codex +1 ★ 267repo stars design-patterns-implementation aj-geddes design-patterns-implementation — a skill for Claude Code and Codex that picks and applies design patterns to architectural problems. It kicks in during refactoring, architecture review, and when building extensible systems. CX Codex +1 601installs create-implementation-plan official github The create-implementation-plan skill creates a Markdown implementation plan for features, refactoring, package upgrades, or infrastructure work. Use it when an agent needs an explicit task breakdown. CX Codex +1 12,558installs implementation-design-patterns pproenca implementation-design-patterns is a Claude Code skill that identifies a Gang of Four pattern from a problem description and explains when to apply or avoid it. CX Codex +1 151installs figure-it-out backnotprop figure-it-out — a skill for Claude Code, Codex, Cursor and other platforms that designs a step-by-step playbook when off-the-shelf tools don't fit. Scales rigor to task complexity, runs hypothesis loops, and logs decisions for review. CX Codex +1 10,300installs superpowers-plan anthonylee991 superpowers-plan makes the agent draft an implementation plan with small steps, the files each step touches, and a check for every one. Useful before edits that span several files. CX Codex +1 1installs

From the same set43

The whole set →
code-reviewer The code-reviewer Claude Code subagent reviews completed changes against project requirements, contracts, and quality rules. It runs after implementation or when a review or compliance check is requested. CX Codex ★ 720repo stars solver solver generates distinct fixes for verified root causes and evaluates tradeoffs. Helps select the right remedy strategy once cause investigation finishes. CX Codex ★ 720repo stars design-sync design-sync compares Design Docs to flag incompatible shared requirements and returns a structured report. Use it when several design documents need a consistency check. CX Codex ★ 720repo stars security-reviewer security-reviewer weighs finished code against the security rules your project set for itself and answers with the fixes that cannot be skipped. CX Codex ★ 720repo stars recipe-front-adjust recipe-front-adjust — a skill for Claude Code adjusts already implemented frontend components and verifies them against the design source. It executes interactive refinement cycles directly within the active session. CX Codex +1 ★ 720repo stars prd-creator prd-creator turns a feature idea into a PRD with user stories, an MVP boundary and success metrics, after a short round of questions. CX Codex ★ 720repo stars verifier verifier evaluates debugging investigation results using the Devil's Advocate method, validates failure points, and checks path coverage. CX Codex ★ 720repo stars frontend-ai-guide The frontend-ai-guide skill reviews React and TypeScript work for design problems, debugging gaps, and incomplete frontend behavior. CX Codex +1 ★ 720repo stars

Project sponsors

Companies that keep this analytics open