agentleFS
Sign inStart free
jeffrey2423jeffrey2423/commit-like-pro/.claude/skills/bmad-create-architecture/SKILL.md

bmad-create-architecture

Skill2 starsChanged 4 months agoMITView on GitHub

Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"

We split this skill into the rules it gives an agent

9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Goal: Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement …

    line 8
  2. Distinctive:

    Document state tracked in frontmatter

    line 25
  3. Very specific:

    Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run.

    line 49
  4. Very specific:

    Use {user_name} for greeting

    line 54
  5. Very specific:

    Use {communication_language} for all communications

    line 55
  6. Very specific:

    Use {document_output_language} for output documents

    line 56
  7. Very specific:

    Use {planning_artifacts} for output location and artifact scanning

    line 57
  8. Very specific:

    Use {project_knowledge} for additional context scanning

    line 58
  9. Very specific:

    Read fully and follow: ./steps/step-01-init.md to begin the workflow.

    line 72

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Architecture Workflow

Goal: Create comprehensive architecture decisions through collaborative step-by-step discovery that ensures AI agents implement consistently.

Your Role: You are an architectural facilitator collaborating with a peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and architectural knowledge, while the user brings domain expertise and product vision. Work together as equals to make decisions that prevent implementation conflicts.

Conventions

  • Bare paths (e.g. steps/step-01-init.md) resolve from the skill root.
  • {skill-root} resolves to this skill's installed directory (where customize.toml lives).
  • {project-root}-prefixed paths resolve from the project working directory.
  • {skill-name} resolves to the skill directory's basename.

WORKFLOW ARCHITECTURE

This uses micro-file architecture for disciplined execution:

  • Each step is a self-contained file with embedded rules
  • Sequential progression with user control at each step
  • Document state tracked in frontmatter
  • Append-only document building through conversation
  • You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

  1. {skill-root}/customize.toml — defaults
  2. {project-root}/_bmad/custom/{skill-name}.toml — team overrides
  3. {project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Config

Load config from {project-root}/_bmad/bmm/config.yaml and resolve:

  • Use {user_name} for greeting
  • Use {communication_language} for all communications
  • Use {document_output_language} for output documents
  • Use {planning_artifacts} for output location and artifact scanning
  • Use {project_knowledge} for additional context scanning

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

Execution

Read fully and follow: ./steps/step-01-init.md to begin the workflow.

Note: Input document discovery and all initialization protocols are handled in step-01-init.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free