beads-architect

Generate structured architecture consults for Beads tasks with risk assessment and phased plans.

Updated Jan 26, 2026

Search Tags:#design #architecture #beads #risk-assessment #api-design #consult #datamodel

Ready to run

npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-architect
Source: https://github.com/vega113/beads-orchestration-skills/tree/main/beads-architect
Command: npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provide structured architectural guidance for Beads tasks, clarifying boundaries, trade-offs, and an implementable plan that other agents can execute during architecture decisions, cross-cutting refactors, API design, or data-model changes.

Core Features & Use Cases

Architecture consult workflow: read task context, draft a consult using the architect template, and share actionable guidance with risk analysis.
Structured output: include constraints, recommended approach, trade-offs, alternatives considered, and a step-by-step implementation plan, ready for Beads subtasks.
Reuse and collaboration: leverage templates and reference examples to align cross-team decisions.

Quick Start

Draft an architecture consult for a Beads task using the architect template to outline the recommended approach, boundaries, and milestones.

Frequently Asked Questions about beads-architect

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

FAQPage Schema

How do I plan an API design refactor with risk assessment and phased implementation?▼

To plan an API design refactor with risk assessment, generate a structured architecture consult that outlines constraints, recommended approaches, trade-offs, alternatives, and step-by-step milestones for phased implementation. This provides a clear, handoff-ready plan for cross-cutting changes.

What is the best way to document architecture decisions for cross-cutting data-model changes?▼

The best way to document architecture decisions for cross-cutting data-model changes is to draft a consult using an architect template. This captures boundaries, trade-offs, and an implementable plan that aligns cross-team decisions and guides subsequent subtasks.

Can I use this approach to guide refactors and API design for my specific platform?▼

Yes, you can use this architecture consult approach to guide refactors and API design for your platform. It generates structured guidance with risk analysis and step-by-step implementation plans specifically tailored for cross-cutting architectural changes.

How does the architecture consult workflow handle scope and constraints for data-model changes?▼

The architecture consult workflow handles scope and constraints by reading task context and drafting a structured consult. It explicitly defines boundaries, constraints, alternatives considered, and milestones to ensure an implementable plan for data-model changes.

When do I need a structured architecture consult for API design?▼

You need a structured architecture consult for API design when making cross-cutting architectural decisions that require risk assessment, clear boundaries, trade-off analysis, and a phased implementation plan ready for downstream execution.