OpenSkillIndex← back to search
claude-code

Awesome-omni-skill ArchitectProtocol

A strict 6-phase development protocol for software architecture, product design, and QA.

install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/architectprotocol" ~/.claude/skills/diegosouzapw-awesome-omni-skill-architectprotocol && rm -rf "$T"
manifest: skills/development/architectprotocol/SKILL.md
source content

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.