domain-feature-design

Validate RFC-driven domain and feature designs for organon constraints before code.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/VledicFranco/organon --skill domain-feature-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-feature-design
Source: https://github.com/VledicFranco/organon/tree/main/.claude/skills/domain-feature-design
Command: npx skills add https://github.com/VledicFranco/organon --skill domain-feature-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain and feature design often suffers from incomplete RFCs that lack explicit organon constraints and a concrete implementation plan. This skill enforces a disciplined approach to RFC-driven evolution by ensuring both organon mutation plans (ETHOS.md, PHILOSOPHY.md) and a detailed technical implementation plan are produced before code is written.

Core Features & Use Cases

  • Enforces dual planning: organon constraints and technical implementation details, so RFCs are complete and actionable.
  • Guides RFC creation for domains, features, or major capabilities, with practical templates and checklists.
  • Supports an update workflow that propagates design decisions into product-level organon files and references.
  • Helps teams reason about scope, invariants, principles, and decision heuristics to drive correct implementations.

Quick Start

Draft a complete RFC skeleton with ETHOS.md, PHILOSOPHY.md, architecture, API, and phased implementation plan.

Frequently Asked Questions about domain-feature-design

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

FAQPage Schema
How do I validate RFC architecture and invariants before coding a new domain feature?

RFC-driven domain design validation ensures architecture, API design, invariants, and risk management sections are detailed and testable before any code is written. This approach enforces dual planning by requiring both organon mutation plans and technical implementation plans to be present.

What is an organon constraint in domain design and when do I need it?

An organon constraint defines the architectural and philosophical boundaries for a domain, typically documented in ETHOS.md and PHILOSOPHY.md files. You need these constraints when designing new domains, features, or major capabilities to ensure correct implementations and complete RFCs.

How to create a complete RFC skeleton with architecture and phased implementation plans?

Draft a complete RFC skeleton by including ETHOS.md, PHILOSOPHY.md, architecture, API, and a phased implementation plan. This dual-planning approach ensures both organon constraints and technical implementation details are defined, making the RFC complete and actionable for development.

Does RFC-driven feature design work for updating existing domain architecture?

RFC-driven feature design supports an update workflow that propagates design decisions into product-level organon files and references. It guides teams to reason about scope, invariants, principles, and decision heuristics to drive correct implementations for new or existing domains.

Why does my domain feature RFC lack a concrete implementation plan?

Incomplete RFCs often lack explicit organon constraints and a detailed technical implementation plan because dual planning was not enforced. RFC-driven design validation checks that both organon mutation plans and technical implementation details are produced before code is written.