implementation-approach

Analyzes project state and risks to identify an implementation strategy with rationale documentation.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/jcchikikomori/opencode-workflow --skill implementation-approach-jcchikikomori
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-approach
Source: https://github.com/jcchikikomori/opencode-workflow/tree/main/skills/implementation-approach
Command: npx skills add https://github.com/jcchikikomori/opencode-workflow --skill implementation-approach-jcchikikomori

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The framework helps teams planning software development by guiding structured decision-making for implementation strategies, including analysis of current state, patterns, risks, constraints, and documentation of decisions.

Core Features & Use Cases

  • Phase-based meta-cognitive analysis to align design goals with business and technical constraints
  • Strategy pattern discovery by researching viable approaches and mapping context to options
  • Risk assessment and constraint verification to ensure safe, measurable transitions
  • Design rationale documentation to capture selected strategy and alternatives for transparency

Quick Start

Provide a project brief and let the framework guide you through current-state analysis, strategy selection, and rationale documentation.

Frequently Asked Questions about implementation-approach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is meta-cognitive analysis for software implementation strategy?

Meta-cognitive analysis for implementation strategy is a structured workflow that evaluates current state, constraints, and risks to guide architecture decisions and document rationale for selected patterns.

How do I choose an implementation pattern for a software project?

To choose an implementation pattern, analyze current state and constraints, explore viable strategy options, map context to patterns, assess risks, and verify constraints before documenting rationale.

How do you document architecture decision rationale for software development?

Document architecture decision rationale by capturing the selected implementation strategy, explored alternatives, verified constraints, and risk mitigation steps to ensure transparency.

Can I use this strategy selection workflow for small projects or is it only for large architecture decisions?

This strategy selection workflow applies to any project seeking structured decision-making for architecture, scaling from small implementations to large systems by analyzing constraints and risks.

When should I not use structured implementation strategy selection?

Avoid structured implementation strategy selection when a project requires immediate, ad-hoc coding without cross-cutting requirements, or when constraint verification and risk assessment are unnecessary for the target architecture.