logical-architecture

Translate actor-behavior models into a component map with data-flow diagrams.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill logical-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logical-architecture
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/logical-architecture
Command: npx skills add https://github.com/rachel353/fullty-plan --skill logical-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transform actor-behavior inputs (requirements, user flows) into a structured, validated logical architecture by identifying components and mapping dependencies.

Core Features & Use Cases

  • Extract actors and actions from input documents to derive cohesive components.
  • Enforce the Primary Responsibility rule and SRP validation for each component.
  • Map requirements to components and link user flows to component interactions.
  • Generate a complete architecture document and data flow diagrams that guide implementation.

Quick Start

Feed your conceptual model and requirements into the workflow to produce a validated logical architecture document and component map.

Frequently Asked Questions about logical-architecture

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

FAQPage Schema
How do I turn requirements into a clean system architecture?▼

Mapping user flows to component interactions involves linking your conceptual model to the derived components. The workflow extracts actors and actions, validates single-responsibility for each component, and documents the precise data flows between them.

What is single-responsibility validation in logical architecture design?▼

Single-responsibility validation in logical architecture design enforces the Primary Responsibility rule for each component. It ensures every extracted component serves one cohesive purpose, preventing overlapping dependencies and maintaining a clean component map.

Do I need a complete conceptual model before designing components?▼

Yes, you need a complete conceptual model before designing components. The workflow applies when your actor-behavior inputs and requirements are ready, using them to extract actors, derive cohesive components, and map dependencies accurately.

How do I generate architecture documentation with data-flow diagrams?▼

To generate architecture documentation with data-flow diagrams, feed your conceptual model and requirements into the workflow. It outputs a complete, validated logical architecture document detailing component relationships and system data flows.

Can I map requirements to existing components or must they be derived from scratch?▼

You can map requirements to components derived directly from your input documents. The workflow extracts actors and actions to identify cohesive components, applies single-responsibility validation, and then maps your requirements to these validated components.