Implementation strategy selection framework with meta-cognitive approach, verification levels, and integration point definitions. Use when planning implementation strategy, selecting development approach, or defining verification criteria.
npxskills add shinpr/claude-code-workflows--skill implementation-approachLoading…
Core Question: "What does the existing implementation look like?"
Architecture Analysis: Responsibility separation, data flow, dependencies, technical debt
Implementation Quality Assessment: Code quality, test coverage, performance, security
Historical Context Understanding: Current form rationale, past decision validity, constraint changes, requirement evolution
Core Question: "When determining before → after, what implementation patterns or strategies should be referenced?"
Research and Exploration: Tech stack examples (WebSearch), similar projects, OSS references, literature/blogs
Creative Thinking: Strategy combinations, constraint-based design, phase division, extension point design
Legacy Handling Strategies:
New Development Strategies:
Integration/Migration Strategies:
Important: The optimal solution is discovered through creative thinking according to each project's context.
Core Question: "What risks arise when applying this to existing implementation, and what's the best way to control them?"
Technical Risks: System impact, data consistency, performance degradation, integration complexity
Operational Risks: Service availability, deployment downtime, process changes, rollback procedures
Project Risks: Schedule delays, learning costs, quality achievement, team coordination
Preventive Measures: Phased migration, parallel operation verification, integration/regression tests, monitoring setup
Incident Response: Rollback procedures, log/metrics preparation, communication system, service continuation procedures
Core Question: "What are this project's constraints?"
Technical Constraints: Library compatibility, resource capacity, mandatory requirements, numerical targets
Temporal Constraints: Deadlines/priorities, dependencies, milestones, learning periods
Resource Constraints: Team/skills, work hours/systems, budget, external contracts
Business Constraints: Market launch timing, customer impact, regulatory compliance
Select optimal solution from basic implementation approaches (creative combinations encouraged):
Characteristics: Vertical implementation across all layers by feature unit Application Conditions: Features share fewer than 2 data models, each feature is independently deliverable, changes touch 3+ architecture layers Verification Method: End-user value delivery at each feature completion
Characteristics: Phased construction by architecture layer Application Conditions: 3+ features depend on a common foundation layer, foundation changes require stability verification before consumers can proceed Verification Method: Integrated operation verification when all foundation layers complete
Characteristics: Flexible combination according to project characteristics Application Conditions: Unclear requirements, need to change approach per phase, transition from prototyping to full implementation Verification Method: Verify at appropriate L1/L2/L3 levels according to each phase's goals
Design Doc Documentation: Record in the Design Doc's implementation approach section:
Priority for completion verification of each task:
Priority: L1 > L2 > L3 in order of verifiability importance
Define integration points according to selected strategy:
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).