architect

Generate implementation specifications from FABER work item requirements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill architect-fractary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
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-fractary

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Architect generates a concrete implementation specification from work-item requirements, documenting technical approach and success criteria.

Core Features & Use Cases

  • Generate implementation specification
  • Post Architect start notification
  • Save and commit the specification
  • Push changes and update session with results

Quick Start

Generate a spec that guides the Build phase and records it in version control.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I generate a technical specification from work item requirements?

Architect generates a detailed implementation specification from work-item requirements, documenting technical approach, design decisions, and success criteria to guide the build phase.

What gets included in a specification generated from requirements?

The specification includes technical design documents, success criteria, and Architecture Decision Records (ADRs) when applicable, all committed to version control.

Can I use this to spec features, bugs, and chores in one workflow?

Yes. Architect applies to /feature, /bug, /chore, and /patch work types, generating specs that satisfy the full workflow lifecycle from Frame results through version control and status updates.

Does this tool handle version control and notifications automatically?

Yes. Architect saves the specification, commits it to version control, pushes to remote, and posts status updates per the workflow requirements.

What do I need to run this before generating a specification?

Architect requires bash and jq as dependencies, and operates on FABER work item requirements as input data.

When should I generate a spec versus documenting design ad hoc?

Generate a spec when you need a structured, committed record of technical approach and success criteria that integrates with your workflow lifecycle and version control.