skills.rest
brianmontero18
brianmontero18COMMUNITY
Explore all skills by this author →
GitHub

architect

Generate executable specifications with verifiable acceptance criteria from codebase context.

1|Updated Mar 1, 2026
Search Tags:#spec#guardrails#architect#acceptance-criteria#codebase-exploration#executable-spec
One-click install
npx skills add https://github.com/brianmontero18/astral --skill architect-brianmontero18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/brianmontero18/astral/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/brianmontero18/astral --skill architect-brianmontero18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague architectural requests into concrete, executable specifications with clearly defined acceptance criteria, reducing ambiguity and accelerating delivery.

Core Features & Use Cases

  • Generates executable specifications driven by codebase context and stakeholder goals.
  • Captures verifiable acceptance criteria and guardrails to prevent scope creep.
  • Reads project artifacts (jiras, PRs, docs) to ground the spec in reality and surface blockers.

Quick Start

Provide a feature description or ticket, and I will generate an executable spec with clear acceptance criteria.

Frequently Asked Questions about architect

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

FAQPage Schema
What is an executable specification with verifiable acceptance criteria?▼

An executable specification transforms vague architectural requests into concrete guardrails and verifiable acceptance criteria, reducing ambiguity and preventing scope creep before coding begins.

How do I create executable specs from existing codebase context and stakeholder requests?▼

You create executable specs by loading project artifacts like Jiras, PRs, and docs to ground the specification in reality, surfacing blockers and defining concrete patterns for the requested feature.

Can I generate architectural guardrails without performing broad refactors or adding new tooling?▼

Yes, you can generate architectural guardrails that explicitly adhere to constraints like no tooling additions and no broad refactors, ensuring the specification stays within current project boundaries.

What is the best way to prevent scope creep when starting software architecture tasks?▼

The best way to prevent scope creep is to define verifiable acceptance criteria and concrete guardrails in an executable specification before development starts, anchoring the scope to stakeholder goals.

Does generating an executable spec require reading existing project artifacts like Jiras and PRs?▼

Yes, generating an executable spec requires reading project artifacts like Jiras, PRs, and docs to explore codebase patterns and ground the final specification in current project realities.

Related Skills

Explore More Software Engineering Skills→
busboom-software-studiobusboom-software-studio
1

project-initiation

Orchestrate the sprint-planner to generate three design documents from a stakeholder specification.

Official
Advanced
saranskumarsaranskumar

gsd-execute

Create a finalized SPEC file and execute the PLAN, EXECUTE, VERIFY, COMMIT workflow.

Community
Advanced
lasswelltlasswellt
1

codebase-map

Analyze a codebase across technology, architecture, quality, and concerns to generate CODEBASE-MAP.md.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

speckit-specify

Generate structured feature specification documents from natural language descriptions.

Community
Intermediate