architect

Plan software architecture decisions and analyses without modifying source code.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/coakenfold/p-100226 --skill architect-coakenfold
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/coakenfold/p-100226/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/coakenfold/p-100226 --skill architect-coakenfold

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Architect Mode provides a planning-only workflow that enables teams to research, analyze, and design high-level software architectures without making any code changes.

Core Features & Use Cases

  • Non-invasive design exploration: Evaluate architectural options, constraints, and technology trade-offs without editing the codebase.
  • High-level design artifacts: Produce architecture overviews, component diagrams, and data-flow sketches suitable for documentation and alignment.
  • Use Case: When planning a migration from monolith to modular services, generate a candidate target architecture and migration plan before touching source files.

Quick Start

Propose a high-level software architecture for a new payment service, including major components and data flows.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I plan software architecture without modifying source code?

Plan software architecture by using a non-invasive workflow that generates structured design plans, evaluation criteria, and architecture documentation without modifying source code. This approach supports design reviews and technology evaluations safely.

What is the best way to design a migration plan from a monolith to modular services?

Designing a migration plan from a monolith to modular services involves producing a candidate target architecture and high-level migration strategy before touching source files. This planning task generates architecture overviews and data-flow sketches for team alignment.

Can I generate architecture overviews and component diagrams for documentation?

Yes, you can generate architecture overviews, component diagrams, and data-flow sketches suitable for documentation. This planning-only workflow produces high-level design artifacts to support design reviews and technology evaluations across projects.

Does the architecture planning workflow evaluate technology trade-offs and constraints?

The architecture planning workflow evaluates architectural options, constraints, and technology trade-offs without editing the codebase. It delivers structured guidance and evaluation criteria to satisfy non-invasive design exploration requirements.

When do I need a non-invasive design exploration for software systems?

You need non-invasive design exploration when planning architectural decisions, evaluating technologies, or conducting design reviews before implementation. It allows teams to research and analyze high-level software architectures and produce documentation-only plans without code changes.

What are the limitations of a planning-only architecture workflow?

The limitation of a planning-only architecture workflow is that it delivers structured plans, guidance, and evaluation criteria but does not modify source code. It is restricted to documentation-only planning tasks and high-level design artifact generation.