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.1 KiB

Raw Blame History

Non-Functional Requirements Assessment

Workflow: bmad-testarch-nfr Version: 5.0 (Step-File Architecture)

Overview

Assess non-functional requirements (performance, security, reliability, maintainability) with evidence-based validation and deterministic PASS/CONCERNS/FAIL outcomes.

WORKFLOW ARCHITECTURE

This workflow uses step-file architecture:

Micro-file Design: Each step is self-contained
JIT Loading: Only the current step file is in memory
Sequential Enforcement: Execute steps in order

INITIALIZATION SEQUENCE

1. Configuration Loading

From workflow.yaml, resolve:

config_source, test_artifacts, user_name, communication_language, document_output_language, date
custom_nfr_categories

2. First Step

Load, read completely, and execute: ./steps-c/step-01-load-context.md

3. Resume Support

If the user selects Resume mode, load, read completely, and execute: ./steps-c/step-01b-resume.md

This checks the output document for progress tracking frontmatter and routes to the next incomplete step.

1.1 KiB Raw Blame History