Enforce architectural validation and documentation before implementation begins.
npx skills add https://github.com/pglemos/GOLFFOX --skill architect-first-pglemos
Please help me install this Agent Skill. Skill: architect-first Source: https://github.com/pglemos/GOLFFOX/tree/main/.claude/skills/architect-first Command: npx skills add https://github.com/pglemos/GOLFFOX --skill architect-first-pglemos
This Skill guides teams to enforce the "Architect-First" development philosophy, ensuring architecture and documentation are completed before implementation begins.
Initiate architectural validation by reviewing the architecture document with this Skill before proceeding to implementation.
High-intent search queries and answers about installing and using this skill.
To enforce architectural validation, you must complete comprehensive system design documentation and run validation scripts before coding begins. This approach ensures all architectural aspects are formally validated and stakeholder-approved, preventing structural issues during complex system planning or refactoring.
The architect-first philosophy mandates that architecture and documentation are fully completed before implementation begins. It facilitates disciplined development by enforcing validation scripts, detailed checklists, and formal documentation templates to maintain high standards in software projects.
Validating architecture documentation involves using detailed checklists and validation scripts to review system designs, data flows, and component descriptions. This process ensures the architecture meets documentation standards and is ready for formal stakeholder approval before development proceeds.
Yes, validation scripts are required for effective deployment of this architecture documentation approach. They automate the enforcement of design standards, ensuring comprehensive diagrams and component descriptions are properly validated before implementation or refactoring begins.
A strict architect-first approach may be unsuitable for rapid prototyping or minor patches where immediate code changes are required. It is designed for planning complex systems or major refactoring where comprehensive documentation and stakeholder validation are necessary.
The best way to plan complex refactoring is to initiate architectural validation by reviewing the architecture document against detailed checklists. This ensures comprehensive diagrams, data flows, and component descriptions are fully validated before implementation proceeds.
ExpeditoJValidate system architecture with documentation, diagrams, and stakeholder consensus.
jr2804Generate architecture diagrams, component descriptions, and data-flow maps from codebases.
ilanf23Organizes design review workflows with gates, checklists, and approval routines.
Dev-Dennis-040Automate rapid prototyping workflows to validate ideas with working MVPs.
