Add Bmad-Method files and some brand-design artifacts!

2026-07-06 18:00:53 +01:00
parent 87bff9c251
commit 2b4a6a413c
1806 changed files with 417144 additions and 0 deletions
@@ -0,0 +1,58 @@
+---
+name: {skill-name}
+description: {one-line summary plus the trigger phrases that should route here, e.g. "Use when the user says X or wants to Y"}
+---
+
+<!-- BUILDER SCAFFOLD GUIDANCE — DELETE THIS WHOLE COMMENT BLOCK BEFORE SHIPPING.
+
+This is a starting point, not a shape to fill in mechanically. Keep the role
+paragraph, the activation block, and whatever the skill actually needs. Cut the
+rest. Every surviving line should beat its own absence.
+
+Pick the archetype that matches what you are building and keep only its parts:
+
+- One-shot action. The skill does a single thing and returns. Keep the role
+  paragraph and a short outcome statement. Drop multi-stage routing, memlog, and
+  resume. Most skills are this; resist adding more.
+
+- Producer of a durable artifact (brief, PRD, report, deck). Keep memlog as the
+  process memory, a finalize beat that distills the memlog into the artifact, and
+  the output-path handling. This is the archetype that earns memlog.
+
+- Multi-intent router. The skill handles a few related jobs behind one entry.
+  Keep an intent table that routes to references, and name the stages with
+  descriptive words, never numbered prefixes.
+
+Customization: only add the resolver activation step and reference
+{workflow.<name>} values if the author accepted customize.toml. If they declined,
+use hardcoded paths and drop the resolver step entirely.
+
+-->
+
+# {skill-name}
+
+{One paragraph stating the destination: the stance the skill acts from, the
+outcome it produces, who consumes that output, and the bar that consumer sets.
+Write it once; do not restate it lower down.}
+
+## Resolution rules
+
+- Bare paths and `{skill-root}` (e.g. `references/guide.md`) resolve from this skill's installed directory.
+- `{project-root}` → the project working directory.
+- `{skill-name}` → the skill directory's basename.
+
+## On Activation
+
+1. Load config from `{project-root}/_bmad/config.yaml` (and `.user.yaml` if present). Use sensible defaults for anything missing rather than requiring configuration.
+
+<!-- Keep step 2 only for artifact-producing skills that carry process memory. -->
+2. Resume check. Look for an existing `.memlog.md` in the run folder. If one is found, read it once to rebuild state and continue append-only; otherwise initialize a new memlog with `uv run {project-root}/_bmad/scripts/memlog.py init --path <run-folder>/.memlog.md`.
+
+<!-- Keep step 3 only if the author accepted customize.toml. -->
+3. Resolve the `workflow` block: run `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. If the script fails, merge these three files yourself in base → team → user order — `{skill-root}/customize.toml`, `{project-root}/_bmad/custom/{skill-name}.toml`, `{project-root}/_bmad/custom/{skill-name}.user.toml` — where scalars override, tables deep-merge, arrays of tables keyed by `code`/`id` replace matching entries and append new ones, and all other arrays append. Reference resolved values as `{workflow.<name>}` everywhere below; never hardcode a path beside a declared scalar.
+
+## {Body}
+
+{The body is whatever the skill needs and nothing more. State each beat as the
+outcome you want, reserving exact procedure for the few places a wrong move costs
+something. Name stages with descriptive words, never numbered prefixes.}