Files

T

football2801 a536baabd6 feat: initial commit — BMAD tooling, Claude memories, firmware scaffold

Adds the complete project foundation:
- BMAD BMM workflow tooling (_bmad/)
- Claude slash commands, skills, and project memories (.claude/)
- ESP32 firmware scaffold (PlatformIO + Waveshare e-ink driver)
- .gitignore excluding _bmad-output/ and .pio/ build artifacts

Planning artifacts (PRD, architecture, epics) are intentionally not
tracked — they live in _bmad-output/ per project convention.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-27 15:38:46 -04:00

1.2 KiB

Raw Blame History

name, description, nextStepFile

name	description	nextStepFile
step-01-assess	Load an existing output for editing	./step-02-apply-edit.md

Step 1: Assess Edit Target

STEP GOAL:

Identify which output should be edited and load it.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

📖 Read the complete step file before taking any action
✅ Speak in {communication_language}

Role Reinforcement:

✅ You are the Master Test Architect

Step-Specific Rules:

🎯 Ask the user which output file to edit
🚫 Do not edit until target is confirmed

EXECUTION PROTOCOLS:

🎯 Follow the MANDATORY SEQUENCE exactly

CONTEXT BOUNDARIES:

Available context: existing outputs
Focus: select edit target
Limits: no edits yet

MANDATORY SEQUENCE

CRITICAL: Follow this sequence exactly.

1. Identify Target

Ask the user to provide the output file path or select from known outputs.

2. Load Target

Read the provided output file in full.

3. Confirm

Confirm the target and proceed to edit.

Load next step: {nextStepFile}

🚨 SYSTEM SUCCESS/FAILURE METRICS:

✅ SUCCESS:

Target identified and loaded

❌ SYSTEM FAILURE:

Proceeding without a confirmed target

1.2 KiB Raw Blame History