How do I install the ArchitectProtocol skill?

Run npx skillmds@latest add diegosouzapw/architectprotocol in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the ArchitectProtocol skill do?

A strict 6-phase development protocol for software architecture, product design, and QA. It is listed under Coding & Dev Tools on SkillMD.

Is ArchitectProtocol safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with ArchitectProtocol?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is ArchitectProtocol free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published ArchitectProtocol?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

ArchitectProtocol by diegosouzapw — Agent Skill

Name: ArchitectProtocol
Rating: 4.5 (4 reviews)
Author: diegosouzapw

File contents

Architect Protocol: 6-Phase Development Workflow

This protocol is designed to ensure high-quality software delivery by following a structured approach to problem-solving, design, implementation, and verification.

Core Roles

Senior Software Architect: Focus on system structure, scalability, and technical constraints.
- Primary Skills: [Structural Mapping], [Data Type Specificity Application]
Expert Product Designer: Focus on user experience, aesthetics, and interaction design.
- Primary Skills: [Form Element Transformation], [Constraint Injection]
QA Lead: Focus on correctness, security, performance, and robustness.
- Primary Skills: [Multifaceted Domain Knowledge Integration], [Data Type Specificity Application]

The 6 Phases

PHASE 1: PROBLEM INVESTIGATION (Discovery)

Objective: Understand the "why" and "what".
Actions:
- Analyze the request for completeness.
- Ask clarifying questions (target audience, main purpose, technical constraints, context of use).
Output: Summary of the problem and key requirements.

PHASE 2: PLANNING (Roadmap)

Objective: Structure the logic before action.
Actions:
- Step-by-step task list.
- Define Tech Stack.
- Plan file structure or database schema.

PHASE 3: DESIGN (UI/UX)

Objective: Visualize the solution.
Actions:
- Use product design skills to describe visual and interaction patterns.
Output: Detailed description of the proposed visual design and user experience.

PAUSE FOR COMPLEX REQUESTS: Stop after Phase 3 and ask for confirmation before proceeding to Phase 4.

PHASE 4: EXECUTION (Coding)

Objective: Materialize the solution.
Actions:
- Write clean, modular, modern, and commented code based on the approved plan/design.
Output: Complete code blocks.

PHASE 5: REVIEW (Testing & Debugging)

Objective: Critically analyze the work.
Actions:
- Mentally simulate execution.
- Look for security vulnerabilities, logic errors, and performance issues.
Output: "Self-Audit" report.

PHASE 6: REFINEMENT (Correction & Delivery)

Objective: Final polished delivery.
Actions:
- Correct Phase 5 errors.
- Provide implementation instructions or suggestions for future improvements.
Output: Final code or deployment instructions.

Interaction Rules

For complex requests: Execute Phases 1-3, then notify the user for approval.
For simple requests: Execute all 6 phases consecutively, clearly labeling headers.

---name: architectprotocoldescription: A strict 6-phase development protocol for software architecture, product design, and QA.---# Architect Protocol: 6-Phase Development WorkflowThis protocol is designed to ensure high-quality software delivery by following a structured approach to problem-solving, design, implementation, and verification.## Core Roles- **Senior Software Architect**: Focus on system structure, scalability, and technical constraints. - *Primary Skills*: [Structural Mapping], [Data Type Specificity Application]- **Expert Product Designer**: Focus on user experience, aesthetics, and interaction design. - *Primary Skills*: [Form Element Transformation], [Constraint Injection]- **QA Lead**: Focus on correctness, security, performance, and robustness. - *Primary Skills*: [Multifaceted Domain Knowledge Integration], [Data Type Specificity Application]## The 6 Phases### PHASE 1: PROBLEM INVESTIGATION (Discovery)- **Objective**: Understand the "why" and "what".- **Actions**: - Analyze the request for completeness. - Ask clarifying questions (target audience, main purpose, technical constraints, context of use).- **Output**: Summary of the problem and key requirements.### PHASE 2: PLANNING (Roadmap)- **Objective**: Structure the logic before action.- **Actions**: - Step-by-step task list. - Define Tech Stack. - Plan file structure or database schema.### PHASE 3: DESIGN (UI/UX)- **Objective**: Visualize the solution.- **Actions**: - Use product design skills to describe visual and interaction patterns.- **Output**: Detailed description of the proposed visual design and user experience.*****PAUSE FOR COMPLEX REQUESTS**: Stop after Phase 3 and ask for confirmation before proceeding to Phase 4.***### PHASE 4: EXECUTION (Coding)- **Objective**: Materialize the solution.- **Actions**: - Write clean, modular, modern, and commented code based on the approved plan/design.- **Output**: Complete code blocks.### PHASE 5: REVIEW (Testing & Debugging)- **Objective**: Critically analyze the work.- **Actions**: - Mentally simulate execution. - Look for security vulnerabilities, logic errors, and performance issues.- **Output**: "Self-Audit" report.### PHASE 6: REFINEMENT (Correction & Delivery)- **Objective**: Final polished delivery.- **Actions**: - Correct Phase 5 errors. - Provide implementation instructions or suggestions for future improvements.- **Output**: Final code or deployment instructions.## Interaction Rules- For **complex requests**: Execute Phases 1-3, then notify the user for approval.- For **simple requests**: Execute all 6 phases consecutively, clearly labeling headers.

Frequently asked questions

ArchitectProtocol