architect

Name: architect
Availability: InStock
Author: nicolas

Creates structured implementation plans with phases, validation criteria, and rollback considerations.

Updated Jan 15, 2026

Search Tags:#planning #architecture #guidelines #checklists #risk-management #design-patterns #phase-planning

Ready to run

npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill architect-nicolas-codemate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/nicolas-codemate/claudeCodeConfig/tree/main/skills/architect
Command: npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill architect-nicolas-codemate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams create clear, robust software architecture plans by providing universal patterns, checklists, and guidelines that prevent architectural drift and ensure plans are well-structured and auditable.

Core Features & Use Cases

Universal phase patterns and checklists to design atomic, reversible, and testable plan phases.
Guidance for dependency management, risk ordering, and validation at every step.
Use Case: When planning a new feature, apply this skill to produce a structured plan with phase headers, expected validations, and rollback considerations.

Quick Start

Describe an implementation plan using the Architect Skill to structure phases, validation criteria, and commit messages.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I create a software architecture plan with atomic phases and rollback considerations?▼

Create a software architecture plan by applying universal phase patterns and checklists to structure atomic, reversible phases. This enforces dependency discipline, validation criteria, rollback considerations, and formal phase headers with conventional commit guidance.

What is the best way to prevent architectural drift when planning a new feature?▼

Preventing architectural drift requires using universal design patterns and checklists during the plan phase. This ensures the implementation plan remains well-structured, auditable, and enforces strict dependency discipline and risk ordering at every step.

How does risk management and dependency discipline work in architecture phase planning?▼

Risk management in phase planning works by ordering implementation steps to isolate failures early. It enforces dependency discipline by validating prerequisites at each step, ensuring atomic phases remain testable and reversible before proceeding.

Can I use universal design patterns to refactor existing feature architectures?▼

Yes, you can use universal design patterns to review and refactor existing feature architectures. Applying structured checklists during the plan phase validates current implementations and generates auditable plans with explicit phase headers and rollback considerations.

When do I need formal phase headers and conventional commit guidance in an implementation plan?▼

You need formal phase headers and conventional commit guidance when an implementation plan requires strict auditability and atomic execution. This structure enforces validation criteria and rollback considerations for every individual phase.

Are there limitations to using universal checklists for software architecture planning?▼

Universal checklists focus on structural plan generation, risk ordering, and dependency validation rather than generating code or executing the implementation. They provide architectural guidelines but do not automate the actual software development or deployment process.