bigpowers 2.1.3 → 2.3.0

package/write-document/SKILL.md

@@ -8,6 +8,8 @@ description: Write, organize, and sync high-integrity technical documents using
 
 Create high-signal technical documentation that serves as an expert collaborator for both humans and AI. This skill enforces the BMAD principles to prevent context rot and ensure architectural durability.
 
+**Distinct from `edit-document`:** Use this skill to create a document that does not yet exist. Use `edit-document` when a document already exists and needs restructuring, clarity, or prose improvements.
+
 > **HARD GATE** — Every document must have a clear "Reason for Existence." If a document doesn't provide actionable leverage for a caller or test, do not create it.
 
 ## The BMAD Principles
@@ -16,7 +18,7 @@ Create high-signal technical documentation that serves as an expert collaborator
 | :--- | :--- |
 | **B**old | Make strong assertions. Define clear boundaries and "Never" rules. No "it might" or "usually." |
 | **M**inimal | High-density, low-filler. **Circuit Breaker**: If the file exceeds 300 lines or the session exceeds 20 turns, you MUST run `terse-mode` and compact state before saving. |
-| **A**ctionable | Link every doc to a verifiable outcome. **Architectural Docs**: Verify via Gherkin features (`specs/audit/features/`) or grep-based structure checks (`grep -c "pattern" file`) that prove the design's *constraints* are present. |
+| **A**ctionable | Link every doc to a verifiable outcome. **Architectural Docs**: Verify via Gherkin features (`specs/verifications/features/`) or grep-based structure checks (`grep -c "pattern" file`) that prove the design's *constraints* are present. |
 | **D**urable | Design for the long-term. **Scalability**: Use "Nested Indexing"—root files link to module-level `GEMINI.md` indexes; do not list individual sub-files in the root. |
 
 ## Process
@@ -27,7 +29,7 @@ Choose the correct BMAD-BigPowers artifact:
 - **Decision Record (ADR)**: For "Why" decisions (saved to `specs/adr/`).
 - **Context Map**: For system-wide architectural mapping (`specs/tech-architecture/tech-stack.md`).
 - **Technical Guide**: For "How-to" with verification (saved to `<module>/REFERENCE.md`).
-- **Behavioral Feature**: Gherkin-style compliance specs (saved to `specs/audit/features/`).
+- **Behavioral Feature**: Gherkin-style compliance specs (saved to `specs/verifications/features/`).
 - **Project README**: Project-facing documentation (saved to `README.md` at project root).
 
 **Cross-Cutting Concerns**: If a doc affects multiple modules, place the authoritative source in the lowest common ancestor directory and use "Delegates" (one-line pointers) in sub-directories to maintain the Single Source of Truth without violating the Stepdown Rule.