skills.rest
hitoshiseki
hitoshisekiCOMMUNITY
Explore all skills by this author →
GitHub

architect-first

Enforce architectural design and documentation before implementation code.

Updated May 4, 2026
Search Tags:#code quality#system design#test-driven development#technical debt#software architecture#architect-first#zero coupling
One-click install
npx skills add https://github.com/hitoshiseki/jutsu-simulator --skill architect-first-hitoshiseki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-first
Source: https://github.com/hitoshiseki/jutsu-simulator/tree/main/.claude/skills/architect-first
Command: npx skills add https://github.com/hitoshiseki/jutsu-simulator --skill architect-first-hitoshiseki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the common issue of rushed, poorly planned software development that leads to accumulating technical debt, unintended capability loss, and unmaintainable system structures. It enforces a strict workflow where complete architectural design and documentation are finalized before any implementation code is written, eliminating costly rework and ensuring long-term system maintainability.

Core Features & Use Cases

  • Architect-First Workflow Enforcement: Mandates complete design, documentation, and multi-stakeholder validation of all structural decisions before coding begins.
  • Zero-Coupling Guarantee: Validates that all modules and expansion packs remain fully independent, with no hardcoded cross-module dependencies.
  • Test-Backed Quality Escape Hatch: Allows pragmatic, rapid implementation of non-structural work as long as comprehensive test coverage and logging are in place to act as a safety net.
  • Use Case: Ideal for teams starting new feature development, refactoring legacy systems, or making high-impact architectural changes that require alignment across product, engineering, and stakeholder teams.

Quick Start

Use the architect-first skill to guide the design, validation, and documentation of the new payment processing system before writing any implementation code.

Frequently Asked Questions about architect-first

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

FAQPage Schema
How does enforcing architectural design before implementation prevent technical debt?▼

Enforcing architectural design before implementation prevents technical debt by mandating complete documentation and multi-stakeholder validation of structural decisions, ensuring system maintainability and eliminating costly rework before any code is written.

How do I validate zero coupling between modules during system refactoring?▼

Validate zero coupling during system refactoring by checking that all modules and expansion packs remain fully independent, ensuring there are no hardcoded cross-module dependencies that compromise the architectural structure.

Can I use test-driven development to bypass full architectural design for non-structural features?▼

Test-driven development allows pragmatic, rapid implementation of non-structural work without full architectural design, provided comprehensive test coverage and logging act as a safety net for quality assurance.

What is the best way to align engineering and product teams on high-impact architectural changes?▼

The best way to align teams on high-impact architectural changes is applying an architect-first workflow that requires multi-stakeholder validation and complete documentation of structural decisions prior to coding.

Does the architect-first workflow require specific testing frameworks to enforce its quality escape hatch?▼

The architect-first quality escape hatch requires comprehensive test coverage and logging to act as a safety net, but does not mandate specific testing frameworks, allowing flexible pragmatic code execution for non-structural work.

When should I not use a strict architect-first approach for software development?▼

A strict architect-first approach should not be used for rapid, non-structural work where comprehensive test coverage and logging are already in place, as the test-backed quality escape hatch allows pragmatic implementation without full design documentation.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
GustaPaesGustaPaes

architect-first

Plan and validate architecture before writing implementation code.

Community
Advanced
viktorbezdekviktorbezdek
10

moai-workflow-testing

Automate end-to-end development workflows integrating testing, debugging, profiling, and code review.

Community
Advanced
caiohbfurtadocaiohbfurtado

brainstorming

Facilitate collaborative design and requirement specification for software features.

Community
Advanced