feature-design

Generate a feature scope plan with phases, domain concepts, and implementation contracts.

Updated Jul 6, 2020

Search Tags:#scoping #ddd #roadmap #product-management #hexagonal-architecture #feature-design

Ready to run

npx skills add https://github.com/guifry/devconfig --skill feature-design-guifry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-design
Source: https://github.com/guifry/devconfig/tree/main/claude/skills/feature-design
Command: npx skills add https://github.com/guifry/devconfig --skill feature-design-guifry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables teams to generate a rigorous, implementation-ready feature scope using product thinking, domain-driven design, and hexagonal architecture, ensuring any feature starts with a clear plan and safe boundaries.

Core Features & Use Cases

Phase-driven guidance: Phase 1 (Product Scope), Phase 2 (Architecture Decisions), Phase 3 (Implementation Contract), and Phase 4 (Convention Compliance) to produce a complete plan.
Collaboration and checks: strategist roles and a roundtable simulate debates to surface blind spots and align stakeholders.
Deliverables: a bounded context decision, domain models and services, ports and adapters outlines, data schema, and a concrete implementation contract ready for engineering teams.

Quick Start

Provide a complete feature-scope plan for a requested feature based on a concise brief.

Frequently Asked Questions about feature-design

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

FAQPage Schema

How do I scope a product feature using domain-driven design?▼

Feature scoping with domain-driven design applies a phased approach to translate product thinking into bounded contexts, domain models, and hexagonal architecture boundaries. It yields an implementation-ready plan with safe architectural boundaries.

How do I map hexagonal architecture ports and adapters for a new feature?▼

Map hexagonal architecture ports and adapters by defining the bounded context and domain services first, then outlining the specific ports and adapters needed to isolate the core domain. This produces a concrete implementation contract for engineering teams.

What is the best way to structure a roadmap for a complex product capability?▼

The best way to structure a roadmap for a complex product capability is a four-phase plan: product scope, architecture decisions, implementation contract, and convention compliance. This ensures alignment between product management and engineering teams.

Can I use hexagonal architecture to align engineering and product management teams?▼

Yes, you can use hexagonal architecture to align engineering and product management by establishing safe boundaries and a shared implementation contract. A simulated roundtable of strategist roles surfaces blind spots and aligns stakeholders during feature scoping.

What deliverables do I need for an implementation-ready feature scope plan?▼

Deliverables for an implementation-ready feature scope plan include a bounded context decision, domain models and services, ports and adapters outlines, a data schema, and a concrete implementation contract ready for engineering teams.

When should I not use hexagonal architecture for feature design?▼

You should avoid hexagonal architecture for feature design when a feature request is too early-stage or simple to require strict separation of domain logic from external dependencies, as the overhead of defining ports and adapters may outweigh the benefits.