the-architect

Produce specs, task decompositions, and ADRs before coding.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/fworks-tech/agenthood --skill the-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-architect
Source: https://github.com/fworks-tech/agenthood/tree/main/members/the-architect
Command: npx skills add https://github.com/fworks-tech/agenthood --skill the-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before implementing significant features, teams often struggle with vague requirements and ambiguous design choices. The Architect provides a structured, spec-first workflow that forces clear problem statements, planned solutions, and documented decisions before any implementation begins.

Core Features & Use Cases

  • Spec-driven development: produces a detailed spec.md that captures the problem, proposed solution, scope, acceptance criteria, testing strategy, and open questions.
  • Task decomposition: breaks the spec into small, auditable tasks with one-commit-per-task granularity and explicit dependencies.
  • Architecture decisions: creates Architecture Decision Records (ADRs) that record context, decisions, alternatives considered, consequences, and status.
  • Interview mode: runs a structured clarifying process to reach high confidence before drafting the spec.

Quick Start

Invoke the Architect to start an interview-driven spec and decompose it into actionable tasks.

Frequently Asked Questions about the-architect

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

FAQPage Schema
How do I write technical specs and break down complex features before coding?

An interview-driven workflow runs a structured clarifying process to elicit requirements and reach high confidence, ensuring ambiguous design choices are resolved before drafting the final spec.md and task breakdown.

What is the best way to document architecture decisions for cross-functional planning?

Yes, task decomposition enforces one-commit-per-task granularity with explicit dependencies, ensuring each planned unit of work remains small and auditable from spec to implementation.

How do I enforce a one-commit-per-task workflow for structured software engineering?

Task decomposition breaks the spec into small, auditable tasks with one-commit-per-task granularity and explicit dependencies, ensuring structured implementation that maps directly to the planned design.

Can I use an interview mode to elicit clear requirements for vague software projects?

An interview mode runs a structured clarifying process to elicit clear requirements and reach high confidence, resolving ambiguous design choices before drafting the spec.md file.

When do I need spec-first design and architecture decision records?

Spec-first design is needed for complex features requiring cross-functional planning and explicit design decisions, resolving vague requirements and ambiguous architecture choices before implementation begins.