skills.rest
markerikson
markeriksonCOMMUNITY
Explore all skills by this author →
Website𝕏@acemarkeGitHub

feature-design

Create detailed feature design documents with options analysis and implementation phases.

41|4|Updated May 6, 2026
Search Tags:#architecture#feature design#technical documentation#options analysis#migration planning#implementation phases
One-click install
npx skills add https://github.com/markerikson/opencode-config-example --skill feature-design-markerikson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-design
Source: https://github.com/markerikson/opencode-config-example/tree/main/config/skill/feature-design
Command: npx skills add https://github.com/markerikson/opencode-config-example --skill feature-design-markerikson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prevent costly rework by creating clear, decision-focused feature design documents before implementation, especially for migrations and architecture changes.

Core Features & Use Cases

  • Upfront planning for significant work: Turn an idea into a structured plan with phases, interfaces, and integration points.
  • Options analysis with trade-offs: Compare multiple approaches using criteria, risks, effort, and future flexibility to choose a recommended path.
  • Implementation-ready documentation: Produce a living document with current state, technical design, open questions, and testable phase deliverables.

Quick Start

Use the feature-design skill to produce a design document for a new multi-day feature migration, including an options analysis, a recommended approach, and phased implementation plan.

Frequently Asked Questions about feature-design

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

FAQPage Schema
How do I create a technical design document for a multi-day feature migration?▼

To create a technical design document for a multi-day feature migration, structure a living document with an executive summary, current state analysis, options comparison, recommended approach, technical design, and phased implementation plan.

What is the best way to compare technical options when planning architecture changes?▼

The best way to compare technical options for architecture changes is to evaluate multiple approaches using structured criteria, assessing risks, effort, and future flexibility to clearly identify a recommended path.

Why do I need feature design before implementation?▼

You need feature design before implementation to prevent costly rework and reduce ambiguity by creating clear, decision-focused documentation that defines interfaces, integration points, and testable phase deliverables upfront.

How do I structure implementation phases for a complex feature development?▼

Structure implementation phases for complex feature development by breaking the recommended technical design into sequential, testable deliverables that track integration points and progressively build out the target architecture.

What sections should be included in an architecture migration plan?▼

An architecture migration plan should include an executive summary, current state analysis, options analysis with comparison, recommended approach, technical design, implementation phases, and a list of open questions.

Related Skills

Explore More Software Engineering Skills→
ryosukesutoryosukesuto
1

vibe-start

Draft a design.md file and organize context for AI code review.

Community
Intermediate
shopsysshopsys
349

create-plan

Generate iterative implementation plans from codebase patterns and Jira tickets.

Official
Advanced
JulianKerignardJulianKerignard

TDD Unity

Generate a Technical Design Document for Unity projects using MCP Unity.

Community
Advanced
drgaciwdrgaciw

architecture-decision-records

Create and manage Architecture Decision Records using multiple templates.

Community
Intermediate