- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add shinpr/claude-code-workflows --skill implementation-approach -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add shinpr/claude-code-workflows --skill implementation-approach -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add shinpr/claude-code-workflows --skill implementation-approach -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add shinpr/claude-code-workflows --skill implementation-approach -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/shinpr/claude-code-workflows/tree/HEAD/dev-skills/skills/implementation-approachVom Herausgeber
Core Question: "What does the existing implementation look like?"
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
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.
Complete these steps in order before selecting an implementation strategy:
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.
Core Question: "When determining before → after, what implementation patterns or strategies should be referenced?"
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
Legacy Handling Strategies:
New Development Strategies:
Integration/Migration Strategies:
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.
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.
Technical Risks: System impact, data consistency, performance degradation, integration complexity
Operational Risks: Service availability, deployment downtime, process changes, rollback procedures
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.
Technical Constraints: Library compatibility, resource capacity, mandatory requirements, numerical targets
Temporal Constraints: Deadlines/priorities, dependencies, milestones, learning periods
Select the implementation approach that directly fits the verified dependency and delivery constraints:
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
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
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
Record in the applicable implementation or design decision record:
Alternatives remain active analysis unless an accepted ADR owns them as decision history.
Priority for completion verification of each task:
Priority: L1 > L2 > L3 in order of verifiability importance
Define integration points according to selected strategy:
Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
---name: implementation-approachdescription: Implementation strategy selection framework. Use when planning implementation strategy, selecting development…---# dev-skills/skills/implementation-approach/SKILL.mdFAQ
Laden Sie dev-skills/skills/implementation-approach/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/shinpr/claude-code-workflows.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.