bmad-method 6.8.1-next.9 → 6.9.0

package/src/bmm-skills/3-solutioning/bmad-create-architecture/steps/step-07-validation.md

@@ -1,361 +0,0 @@
-# Step 7: Architecture Validation & Completion
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS treat this as collaborative discovery between architectural peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on validating architectural coherence and completeness
-- ✅ VALIDATE all requirements are covered by architectural decisions
-- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- ✅ Run comprehensive validation checks on the complete architecture
-- ⚠️ Present A/P/C menu after generating validation results
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to address complex architectural issues found during validation
-- **P (Party Mode)**: Bring multiple perspectives to resolve validation concerns
-- **C (Continue)**: Save the validation results and complete the architecture
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Invoke the `bmad-advanced-elicitation` skill
-- When 'P' selected: Invoke the `bmad-party-mode` skill
-- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
-- User accepts/rejects protocol changes before proceeding
-
-## CONTEXT BOUNDARIES:
-
-- Complete architecture document with all sections is available
-- All architectural decisions, patterns, and structure are defined
-- Focus on validation, gap analysis, and coherence checking
-- Prepare for handoff to implementation phase
-
-## YOUR TASK:
-
-Validate the complete architecture for coherence, completeness, and readiness to guide AI agents through consistent implementation.
-
-## VALIDATION SEQUENCE:
-
-### 1. Coherence Validation
-
-Check that all architectural decisions work together:
-
-**Decision Compatibility:**
-
-- Do all technology choices work together without conflicts?
-- Are all versions compatible with each other?
-- Do patterns align with technology choices?
-- Are there any contradictory decisions?
-
-**Pattern Consistency:**
-
-- Do implementation patterns support the architectural decisions?
-- Are naming conventions consistent across all areas?
-- Do structure patterns align with technology stack?
-- Are communication patterns coherent?
-
-**Structure Alignment:**
-
-- Does the project structure support all architectural decisions?
-- Are boundaries properly defined and respected?
-- Does the structure enable the chosen patterns?
-- Are integration points properly structured?
-
-### 2. Requirements Coverage Validation
-
-Verify all project requirements are architecturally supported:
-
-**From Epics (if available):**
-
-- Does every epic have architectural support?
-- Are all user stories implementable with these decisions?
-- Are cross-epic dependencies handled architecturally?
-- Are there any gaps in epic coverage?
-
-**From FR Categories (if no epics):**
-
-- Does every functional requirement have architectural support?
-- Are all FR categories fully covered by architectural decisions?
-- Are cross-cutting FRs properly addressed?
-- Are there any missing architectural capabilities?
-
-**Non-Functional Requirements:**
-
-- Are performance requirements addressed architecturally?
-- Are security requirements fully covered?
-- Are scalability considerations properly handled?
-- Are compliance requirements architecturally supported?
-
-### 3. Implementation Readiness Validation
-
-Assess if AI agents can implement consistently:
-
-**Decision Completeness:**
-
-- Are all critical decisions documented with versions?
-- Are implementation patterns comprehensive enough?
-- Are consistency rules clear and enforceable?
-- Are examples provided for all major patterns?
-
-**Structure Completeness:**
-
-- Is the project structure complete and specific?
-- Are all files and directories defined?
-- Are integration points clearly specified?
-- Are component boundaries well-defined?
-
-**Pattern Completeness:**
-
-- Are all potential conflict points addressed?
-- Are naming conventions comprehensive?
-- Are communication patterns fully specified?
-- Are process patterns (error handling, etc.) complete?
-
-### 4. Gap Analysis
-
-Identify and document any missing elements:
-
-**Critical Gaps:**
-
-- Missing architectural decisions that block implementation
-- Incomplete patterns that could cause conflicts
-- Missing structural elements needed for development
-- Undefined integration points
-
-**Important Gaps:**
-
-- Areas that need more detailed specification
-- Patterns that could be more comprehensive
-- Documentation that would help implementation
-- Examples that would clarify complex decisions
-
-**Nice-to-Have Gaps:**
-
-- Additional patterns that would be helpful
-- Supplementary documentation
-- Tooling recommendations
-- Development workflow optimizations
-
-### 5. Address Validation Issues
-
-For any issues found, facilitate resolution:
-
-**Critical Issues:**
-"I found some issues that need to be addressed before implementation:
-
-{{critical_issue_description}}
-
-These could cause implementation problems. How would you like to resolve this?"
-
-**Important Issues:**
-"I noticed a few areas that could be improved:
-
-{{important_issue_description}}
-
-These aren't blocking, but addressing them would make implementation smoother. Should we work on these?"
-
-**Minor Issues:**
-"Here are some minor suggestions for improvement:
-
-{{minor_issue_description}}
-
-These are optional refinements. Would you like to address any of these?"
-
-### 6. Generate Validation Content
-
-Prepare the content to append to the document:
-
-#### Content Structure:
-
-```markdown
-## Architecture Validation Results
-
-### Coherence Validation ✅
-
-**Decision Compatibility:**
-{{assessment_of_how_all_decisions_work_together}}
-
-**Pattern Consistency:**
-{{verification_that_patterns_support_decisions}}
-
-**Structure Alignment:**
-{{confirmation_that_structure_supports_architecture}}
-
-### Requirements Coverage Validation ✅
-
-**Epic/Feature Coverage:**
-{{verification_that_all_epics_or_features_are_supported}}
-
-**Functional Requirements Coverage:**
-{{confirmation_that_all_FRs_are_architecturally_supported}}
-
-**Non-Functional Requirements Coverage:**
-{{verification_that_NFRs_are_addressed}}
-
-### Implementation Readiness Validation ✅
-
-**Decision Completeness:**
-{{assessment_of_decision_documentation_completeness}}
-
-**Structure Completeness:**
-{{evaluation_of_project_structure_completeness}}
-
-**Pattern Completeness:**
-{{verification_of_implementation_patterns_completeness}}
-
-### Gap Analysis Results
-
-{{gap_analysis_findings_with_priority_levels}}
-
-### Validation Issues Addressed
-
-{{description_of_any_issues_found_and_resolutions}}
-
-### Architecture Completeness Checklist
-
-Mark each item `[x]` only if validation confirms it; leave `[ ]` if it is missing, partial, or unverified. Any unchecked item must be reflected in the Gap Analysis above and in the Overall Status below.
-
-**Requirements Analysis**
-
-- [ ] Project context thoroughly analyzed
-- [ ] Scale and complexity assessed
-- [ ] Technical constraints identified
-- [ ] Cross-cutting concerns mapped
-
-**Architectural Decisions**
-
-- [ ] Critical decisions documented with versions
-- [ ] Technology stack fully specified
-- [ ] Integration patterns defined
-- [ ] Performance considerations addressed
-
-**Implementation Patterns**
-
-- [ ] Naming conventions established
-- [ ] Structure patterns defined
-- [ ] Communication patterns specified
-- [ ] Process patterns documented
-
-**Project Structure**
-
-- [ ] Complete directory structure defined
-- [ ] Component boundaries established
-- [ ] Integration points mapped
-- [ ] Requirements to structure mapping complete
-
-### Architecture Readiness Assessment
-
-**Overall Status:** {{READY FOR IMPLEMENTATION | READY WITH MINOR GAPS | NOT READY}} (choose READY FOR IMPLEMENTATION only when all 16 checklist items are `[x]` and no Critical Gaps remain; choose NOT READY when any Critical Gap is open or any Requirements Analysis or Architectural Decisions item is unchecked; otherwise READY WITH MINOR GAPS)
-
-**Confidence Level:** {{high/medium/low}} based on validation results
-
-**Key Strengths:**
-{{list_of_architecture_strengths}}
-
-**Areas for Future Enhancement:**
-{{areas_that_could_be_improved_later}}
-
-### Implementation Handoff
-
-**AI Agent Guidelines:**
-
-- Follow all architectural decisions exactly as documented
-- Use implementation patterns consistently across all components
-- Respect project structure and boundaries
-- Refer to this document for all architectural questions
-
-**First Implementation Priority:**
-{{starter_template_command_or_first_architectural_step}}
-```
-
-### 7. Present Content and Menu
-
-Show the validation results and present choices:
-
-"I've completed a comprehensive validation of your architecture.
-
-**Validation Summary:**
-
-- ✅ Coherence: All decisions work together
-- ✅ Coverage: All requirements are supported
-- ✅ Readiness: AI agents can implement consistently
-
-**Here's what I'll add to complete the architecture document:**
-
-[Show the complete markdown content from step 6]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Address any complex architectural concerns
-[P] Party Mode - Review validation from different implementation perspectives
-[C] Continue - Complete the architecture and finish workflow
-
-### 8. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
-
-- Invoke the `bmad-advanced-elicitation` skill with validation issues
-- Process enhanced solutions for complex concerns
-- Ask user: "Accept these architectural improvements? (y/n)"
-- If yes: Update content, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
-- Invoke the `bmad-party-mode` skill with validation context
-- Process collaborative insights on implementation readiness
-- Ask user: "Accept these changes to the validation results? (y/n)"
-- If yes: Update content, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
-- Append the final content to `{planning_artifacts}/architecture.md`
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
-- Load `./step-08-complete.md`
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to the document using the structure from step 6.
-
-## SUCCESS METRICS:
-
-✅ All architectural decisions validated for coherence
-✅ Complete requirements coverage verified
-✅ Implementation readiness confirmed
-✅ All gaps identified and addressed
-✅ Comprehensive validation checklist completed
-✅ A/P/C menu presented and handled correctly
-✅ Content properly appended to document when C selected
-
-## FAILURE MODES:
-
-❌ Skipping validation of decision compatibility
-❌ Not verifying all requirements are architecturally supported
-❌ Missing potential implementation conflicts
-❌ Not addressing gaps found during validation
-❌ Providing incomplete validation checklist
-❌ Not presenting A/P/C menu after content generation
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## NEXT STEP:
-
-After user selects 'C' and content is saved to document, load `./step-08-complete.md` to complete the workflow and provide implementation guidance.
-
-Remember: Do NOT proceed to step-08 until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/bmm-skills/3-solutioning/bmad-create-architecture/steps/step-08-complete.md

@@ -1,82 +0,0 @@
-# Step 8: Architecture Completion & Handoff
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- ✅ ALWAYS treat this as collaborative completion between architectural peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on successful workflow completion and implementation handoff
-- 🎯 PROVIDE clear next steps for implementation phase
-- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 🎯 Present completion summary and implementation guidance
-- 📖 Update frontmatter with final workflow state
-- 🚫 THIS IS THE FINAL STEP IN THIS WORKFLOW
-
-## YOUR TASK:
-
-Complete the architecture workflow, provide a comprehensive completion summary, and guide the user to the next phase of their project development.
-
-## COMPLETION SEQUENCE:
-
-### 1. Congratulate the User on Completion
-
-Both you and the User completed something amazing here - give a summary of what you achieved together and really congratulate the user on a job well done.
-
-### 2. Update the created document's frontmatter
-
-```yaml
-stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]
-workflowType: 'architecture'
-lastStep: 8
-status: 'complete'
-completedAt: '{{current_date}}'
-```
-
-### 3. Next Steps Guidance
-
-Architecture complete. Invoke the `bmad-help` skill.
-
-Upon Completion of task output: offer to answer any questions about the Architecture Document.
-
-
-## SUCCESS METRICS:
-
-✅ Complete architecture document delivered with all sections
-✅ All architectural decisions documented and validated
-✅ Implementation patterns and consistency rules finalized
-✅ Project structure complete with all files and directories
-✅ User provided with clear next steps and implementation guidance
-✅ Workflow status properly updated
-✅ User collaboration maintained throughout completion process
-
-## FAILURE MODES:
-
-❌ Not providing clear implementation guidance
-❌ Missing final validation of document completeness
-❌ Not updating workflow status appropriately
-❌ Failing to celebrate the successful completion
-❌ Not providing specific next steps for the user
-❌ Rushing completion without proper summary
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## WORKFLOW COMPLETE:
-
-This is the final step of the Architecture workflow. The user now has a complete, validated architecture document ready for AI agent implementation.
-
-The architecture will serve as the single source of truth for all technical decisions, ensuring consistent implementation across the entire project development lifecycle.
-
-## On Complete
-
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
-
-If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.

package/src/core-skills/bmad-brainstorming/scripts/memlog.py

@@ -1,202 +0,0 @@
-#!/usr/bin/env python3
-# /// script
-# requires-python = ">=3.10"
-# ///
-"""memlog — an append-only memory log: LLM-optimal working memory for a skill.
-
-A memlog is the dense, chronological record of everything that mattered in a piece of
-work — every item the user generated or accepted — kept minimal like human memory: only
-what's important, never bloated. It persists ACROSS sessions, so a fresh session can
-load it and continue. It is NOT a deliverable; downstream artifacts (a brief, a PRD, a
-deck, a report) are *derived* from it on demand. The host skill supplies the vocabulary
-by how it calls `append` — the tool stays neutral.
-
-It is a FLAT log: there are no sections or grouping. Every entry is one line, recorded
-at the END in the order it happened. The chronology itself is the structure — an event
-like "started technique X" is just another entry, same as an idea or an insight.
-
-Two invariants make it trustworthy:
-
-  1. Append-only, chronological. Entries land at the end, in the order they happen.
-     Nothing is ever inserted backward, reordered, or grouped.
-  2. Write-only / blind. Every command is an atomic, context-free write and echoes the
-     new state as JSON, so the caller never re-reads the file mid-session. The one time
-     the file is read is on resume — and the caller reads it itself, not via this script.
-
-The file shape (.memlog.md):
-
-    ---
-    topic: Onboarding flow for a budgeting app
-    goal: lift week-1 retention
-    status: active
-    updated: 2026-05-30T14:22
-    ---
-
-    - (note) user picked techniques: SCAMPER, then Six Thinking Hats
-    - (technique) started SCAMPER
-    - (idea) skip the signup wall: let people try with sample data first
-    - (idea) auto-import one bank account so the first screen shows real numbers
-    - (question) is open-banking consent too heavy for step one?
-    - (technique) started Six Thinking Hats
-    - (idea) black-hat: imported transactions look scary before they're categorized
-    - (insight) the "scary numbers" risk and the "real numbers" idea are one lever: show real data, pre-categorized
-    - (direction) user wants to optimize for the anxious first-timer, not the power user
-    - (decision) lead with one pre-categorized account; defer multi-account import
-
-Each entry may carry an optional `--type` — what KIND it is (idea, insight, question,
-decision, technique, …) — and an optional `--by` naming who it came from (e.g. `user`,
-`coach`), for sessions where authorship matters. Both render into one short inline tag:
-`(idea)`, `(idea by user)`, `(by coach)`. Omit them for a plain note. The host skill
-names the vocabulary; the script does not.
-
-Commands:
-  init   --workspace DIR [--field k=v ...]              create the memlog (errors if it exists)
-  append --workspace DIR --text STR [--type T] [--by W]  append one entry at the end
-  set    --workspace DIR --key K --value V              set/replace a frontmatter field
-
-The workspace is the run folder; the memlog is always {workspace}/.memlog.md.
-"""
-import argparse
-import json
-import os
-import sys
-from datetime import datetime
-from pathlib import Path
-
-MEMLOG = ".memlog.md"
-
-
-def now() -> str:
-    return datetime.now().strftime("%Y-%m-%dT%H:%M")
-
-
-def memlog_path(workspace: str) -> Path:
-    return Path(workspace) / MEMLOG
-
-
-def split(text: str) -> tuple[dict, str]:
-    """Return (frontmatter dict in source order, body str). Frontmatter is plain key: value.
-
-    The closing fence is the first line that is *exactly* `---`, so a `---` inside a
-    field value (topic/goal are free user text) never truncates the frontmatter.
-    """
-    lines = text.splitlines()
-    if not lines or lines[0] != "---":
-        raise ValueError(".memlog.md has no frontmatter")
-    end = next((i for i in range(1, len(lines)) if lines[i] == "---"), None)
-    if end is None:
-        raise ValueError(".memlog.md frontmatter is not terminated")
-    meta: dict[str, str] = {}
-    for line in lines[1:end]:
-        if ":" in line:
-            k, v = line.split(":", 1)
-            meta[k.strip()] = v.strip()
-    return meta, "\n".join(lines[end + 1:]).lstrip("\n")
-
-
-def render(meta: dict, body: str) -> str:
-    # Neutralize newlines in values so a multi-line field can't break the fence on re-read.
-    fm = "\n".join(f"{k}: {' '.join(str(v).splitlines())}" for k, v in meta.items())
-    return "---\n" + fm + "\n---\n\n" + body.rstrip("\n") + "\n"
-
-
-def touch(meta: dict) -> None:
-    """Stamp `updated` and keep it last so the field order stays predictable."""
-    meta.pop("updated", None)
-    meta["updated"] = now()
-
-
-def write_atomic(path: Path, text: str) -> None:
-    tmp = path.with_suffix(path.suffix + ".tmp")
-    tmp.write_text(text, encoding="utf-8")
-    os.replace(tmp, path)
-
-
-def entry_count(body: str) -> int:
-    return sum(1 for ln in body.splitlines() if ln.startswith("- "))
-
-
-def ack(path: Path, meta: dict, body: str) -> None:
-    """Echo new state so the caller never re-reads the file to know where it stands."""
-    print(json.dumps({
-        "ok": True,
-        "memlog": str(path),
-        "status": meta.get("status", ""),
-        "entries": entry_count(body),
-    }))
-
-
-def cmd_init(args) -> int:
-    path = memlog_path(args.workspace)
-    if path.exists():
-        print(f"error: {path} already exists; use append/set to update it", file=sys.stderr)
-        return 2
-    path.parent.mkdir(parents=True, exist_ok=True)
-    meta: dict[str, str] = {}
-    for pair in args.field or []:
-        if "=" not in pair:
-            print(f"error: --field expects key=value, got {pair!r}", file=sys.stderr)
-            return 2
-        k, v = pair.split("=", 1)
-        meta[k.strip()] = v.strip()
-    meta.setdefault("status", "active")
-    touch(meta)
-    write_atomic(path, render(meta, ""))
-    ack(path, meta, "")
-    return 0
-
-
-def cmd_append(args) -> int:
-    path = memlog_path(args.workspace)
-    meta, body = split(path.read_text(encoding="utf-8"))
-    text = " ".join(args.text.split())  # collapse newlines/runs → one-line entry, no prose bloat
-    label = args.type or ""
-    if args.by:
-        label = f"{label} by {args.by}".strip()  # attribution: "(idea by user)" / "(by coach)"
-    tag = f"({label}) " if label else ""
-    entry = f"- {tag}{text}"
-    body = (body.rstrip("\n") + "\n" + entry) if body.strip() else entry  # always at the end
-    touch(meta)
-    write_atomic(path, render(meta, body))
-    ack(path, meta, body)
-    return 0
-
-
-def cmd_set(args) -> int:
-    path = memlog_path(args.workspace)
-    meta, body = split(path.read_text(encoding="utf-8"))
-    meta[args.key] = args.value
-    touch(meta)
-    write_atomic(path, render(meta, body))
-    ack(path, meta, body)
-    return 0
-
-
-def main(argv: list[str] | None = None) -> int:
-    p = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
-    sub = p.add_subparsers(dest="cmd", required=True)
-
-    pi = sub.add_parser("init", help="create the memlog")
-    pi.add_argument("--workspace", required=True)
-    pi.add_argument("--field", action="append", metavar="KEY=VALUE", help="frontmatter field (repeatable)")
-    pi.set_defaults(func=cmd_init)
-
-    pa = sub.add_parser("append", help="append one entry at the end")
-    pa.add_argument("--workspace", required=True)
-    pa.add_argument("--text", required=True)
-    pa.add_argument("--type", help="entry kind, rendered as an inline tag")
-    pa.add_argument("--by", help="who the entry came from (e.g. user, coach); rendered into the tag")
-    pa.set_defaults(func=cmd_append)
-
-    pset = sub.add_parser("set", help="set a frontmatter field")
-    pset.add_argument("--workspace", required=True)
-    pset.add_argument("--key", required=True)
-    pset.add_argument("--value", required=True)
-    pset.set_defaults(func=cmd_set)
-
-    args = p.parse_args(argv)
-    return args.func(args)
-
-
-if __name__ == "__main__":
-    sys.exit(main())