architect

Coordinate software development planning, review, and documentation with multi-agent orchestration.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/roborew/opencode --skill architect-roborew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/roborew/opencode/tree/main/skills/architect
Command: npx skills add https://github.com/roborew/opencode --skill architect-roborew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the software development lifecycle by providing a structured approach to planning, reviewing, and documenting code changes, ensuring quality and maintainability.

Core Features & Use Cases

  • Task Planning: Generates detailed plans for features, bug fixes, and refactors, including stages and ownership.
  • Code Review: Facilitates a thorough review process to ensure adherence to best practices and requirements.
  • Documentation Generation: Creates changelogs, guides, and architecture documentation from completed work.
  • Use Case: Before starting a new feature, use the architect to draft a comprehensive plan, then switch to orchestrate for execution. After implementation, use the architect again to review the changes and generate necessary documentation.

Quick Start

Use the architect skill to create a plan for a new feature.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I plan and document code changes for a new software feature?

Software development planning and documentation for new features can be structured by generating detailed plans, reviewing code changes, and creating changelogs or architecture guides to ensure maintainability and quality.

What is the best way to coordinate code review and debugging tasks?

Coordinating code review and debugging tasks is best handled by a multi-agent orchestration model that enforces strict responsibility boundaries between planning and execution agents to thoroughly review changes against requirements.

How do I generate architecture documentation after a refactoring task?

Architecture documentation after a refactoring task is generated through a post-implementation review process that analyzes completed work to automatically create detailed guides and changelogs reflecting the code changes.

Can I use multi-agent orchestration for both planning and executing a code refactor?

Multi-agent orchestration supports code refactoring by using specialized sub-agents for specific planning tasks while maintaining strict responsibility boundaries between planning and execution agents for the implementation.

Does the planning agent handle the actual code execution during feature development?

The planning agent does not handle code execution; it enforces strict responsibility boundaries between planning and execution agents, meaning you switch to an orchestration tool for execution after drafting the feature development plan.