skills.rest
bryonjacob
bryonjacobCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

software-architecture

Generate chat.md, tasks/, and metadata.json for GitHub issue planning.

1|Updated Oct 21, 2025
Search Tags:#architecture#task breakdown#epic planning#analyze#GitHub issues#design decisions
One-click install
npx skills add https://github.com/bryonjacob/aug --skill software-architecture-bryonjacob
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-architecture
Source: https://github.com/bryonjacob/aug/tree/main/aug-dev/skills/software-architecture
Command: npx skills add https://github.com/bryonjacob/aug --skill software-architecture-bryonjacob

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn vague architectural ideas into concrete planning artifacts for GitHub issues, enabling consistent epic planning and task specification.

Core Features & Use Cases

  • Analyze problem statements to break down scope and propose 2-3 architectural options with trade-offs.
  • ARCHITECT: Define module boundaries, specify interfaces (inputs/outputs/errors), and document key decisions.
  • BREAKDOWN: Propose 3-8 deliverable tasks with acceptance criteria and testing guidance.
  • Output artifacts like chat.md, metadata.json, and task templates for GitHub issues to drive implementation.

Quick Start

Provide an epic/problem description and select a mode (ANALYZE, ARCHITECT, or BREAKDOWN). The skill will generate planning artifacts ready to create GitHub issues.

Frequently Asked Questions about software-architecture

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

FAQPage Schema
How do I break down a vague software architecture idea into GitHub issues?▼

Selecting a mode like ANALYZE, ARCHITECT, or BREAKDOWN processes your problem description to produce structured planning artifacts, including a chat.md file, metadata.json, and task templates for GitHub issues.

What is the best way to document software design decisions and module boundaries?▼

Using the ARCHITECT mode defines module boundaries, specifies interface inputs and outputs, and documents key architectural decisions directly into your project planning files.

Can I generate task acceptance criteria and testing guidance from an epic problem statement?▼

Yes, the BREAKDOWN mode analyzes your epic problem statement to propose 3-8 deliverable tasks complete with acceptance criteria and testing guidance for your team.

How do I analyze architectural options and trade-offs for a software project?▼

Using the ANALYZE mode breaks down the project scope and proposes 2-3 distinct architectural options with detailed trade-offs for your software engineering workflow.

What file formats and planning artifacts do I need for structured epic planning?▼

Structured epic planning requires generating a chat.md file, a metadata.json file, and task templates that capture clear decisions, interfaces, and acceptance criteria.

Do I need any external dependencies to generate architecture task breakdowns?▼

No external dependencies are required to generate architecture task breakdowns; the skill independently processes problem descriptions to output your planning files.

Related Skills

Explore More Software Engineering Skills→
ripabakripabak

breakdown-epic-pm

Convert vague ideas into a comprehensive Epic PRD for architecture planning.

Community
Advanced
psd401psd401
2

triage

Extract FreshService ticket details and create linked GitHub issues.

Official
Intermediate
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
hhhh124hhhhhhhh124hhhh
8

writing-plans

Creates detailed project plans with tasks, milestones, and risk assessments.

Community
Basic