From aidlc-v2
AI-DLC functional-design skill. Produces `business-logic-model.md`, `domain-entities.md`, and `business-rules.md` for a single construction unit, given approved application-design and units-of-work artifacts. Technology-agnostic. Invoke explicitly via `/skill aidlc-functional-design --unit <unit>` when all upstream artifacts exist and only this step is needed. For fresh development intents, activate `aidlc-orchestrator` instead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aidlc-v2:aidlc-functional-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design the detailed business logic for a unit using domain-driven design principles — domain entities, business rules, state lifecycles, and the behavioural model that governs how the unit fulfils the stories mapped to it. Strictly technology-agnostic: captures what the unit does in business terms, not how it is implemented.
Design the detailed business logic for a unit using domain-driven design principles — domain entities, business rules, state lifecycles, and the behavioural model that governs how the unit fulfils the stories mapped to it. Strictly technology-agnostic: captures what the unit does in business terms, not how it is implemented.
This skill refines and deepens the application design. Where application design established component boundaries, methods, and dependencies at a system-wide level, functional design zooms into a single unit and models its internal business logic with enough precision to implement without further clarification.
components.md, component-methods.md, component-dependencies.md, services.md, cross-cutting.md, and any conditional artifacts)units-of-work.md and units-of-work-story-map.md must be availablestories.md must be approvedunits-of-work.md, units-of-work-story-map.mdcomponents.md, component-methods.md, component-dependencies.md, services.md, cross-cutting.mddata-models.md, api-contracts.md, event-catalog.md, external-dependencies.mdstories.mdAnalyse the unit definition, the story mapping, and the application design artifacts first. Derive what you can; ask only where genuine ambiguity remains that would materially affect the quality of the functional design. Focus on:
data-models.md) complete? Are there missing attributes, relationships, or lifecycle rules that the application design left abstract?Three artifacts.
The behavioural model of the unit:
S-<n> IDs from units-of-work-story-map.md), owning componentscomponent-methods.md.event-catalog.md if present.component-dependencies.md for the communication pattern.Detailed entity definitions for all entities owned by this unit's components. Refines and extends data-models.md:
data-models.mdcomponents.mdExplicit catalogue of every business rule:
BR-<n>, sequential within the unitS-<n> IDs this rule supports, traceable via units-of-work-story-map.mdValidation rules for this skill's output live in validation-spec.md at the skill root. See ${CLAUDE_PLUGIN_ROOT}/aidlc-common/protocols/aidlc-validator-protocol.md for how they are applied.
npx claudepluginhub ijin/aidlc-cc-plugin-v2 --plugin aidlc-v2Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.