architect-workflow

Generate implementation specifications from Frame results during Architect phase workflows.

Updated Aug 27, 2026

Search Tags:#architect #version-control #spec-generation

Ready to run

npx skills add https://github.com/fractary/claude-plugins --skill architect-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-workflow
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/faber/skills/architect
Command: npx skills add https://github.com/fractary/claude-plugins --skill architect-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, and includes scripts (resource) components.

What problem does it solve?

Provides the Architect workflow orchestration for FABER, including spec generation, status notifications, and version control integration.

Core Features & Use Cases

Post start notification
Generate and save spec
Commit and push spec changes
Update session with Architect results

Quick Start

Run Architect to produce a formal spec from your Frame results.

Frequently Asked Questions about architect-workflow

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

FAQPage Schema

How do I generate implementation specifications from project requirements?▼

Architect workflow generates formal implementation specifications by processing Frame results—translating requirements into design documents, ADRs, and specs. It handles feature, bug, chore, and patch work types across engineering, design, and data domains, then commits artifacts to version control.

Can I automate spec generation and version control commits in my workflow?▼

Yes. Architect orchestrates spec generation, posts start and completion notifications, commits and pushes specification files to remote repositories as configured, and updates session state—all integrated within the FABER phase.

What does the Architect workflow do with Frame context and requirements?▼

Architect consumes Frame context (title, description, branch) and project requirements, generates a specification file capturing functional and technical requirements plus success criteria, then commits the result to version control with error handling and status reporting.

Do I need version control set up to use Architect workflow?▼

Yes. Architect requires bash and jq as dependencies and integrates with version control systems to commit and push specification artifacts. Remote repository configuration enables automated pushing of generated specs.

How does Architect handle different work types like features and bugs?▼

Architect applies unified spec generation across work types—/feature, /bug, /chore, /patch—translating each into formal specifications with design decisions, ADRs when configured, and success criteria appropriate to the task scope.