@rasensio/aidlc-content 1.3.0 → 1.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.3.0",
+  "version": "1.4.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/20-requirements.md

@@ -27,6 +27,7 @@ Translate the ideation output (or the user's direct request) into precise, testa
    - Specific and unambiguous
    - Testable (an observable outcome)
    - Independent (not relying on unstated assumptions)
+   - **Identified**: write every criterion as a list item `- AC-<n>: <text>` (bold variants `- **AC-<n>**: ...` and `- **AC-<n>:** ...` are also valid). Assign `AC-1`, `AC-2`, ... sequentially. IDs are never renumbered or reused — an amended criterion keeps its meaning or is retired: mark it `- AC-<n> (retired YYYY-MM-DD, superseded by AC-<m>): <text>` and issue a new ID. The testing-phase gate parses these IDs and fails on any active criterion without a referencing test.
 4. **Set scope boundaries.** Explicitly state what is NOT included.
 5. **Non-functional requirements.** Address performance, security, accessibility, and compatibility where relevant.
 6. **For complex input or open decisions**: If requirements are extensive, or unresolved decisions block the draft, create an Input_File in `.aidlc/inbox/` following the User Input Protocol in **aidlc-overview**, rather than asking many sequential questions. Prefer drafting `requirements.md` early with unresolved points marked as explicit decision blocks — users decide better reacting to a concrete draft than answering abstract questions.

package/skills/30-design.md

@@ -21,7 +21,7 @@ Produce a technical design that satisfies the requirements. Define architecture,
 
 ## Instructions
 
-1. **Review requirements.** Read `requirements.md` (or its summary if one exists). Identify the key technical challenges.
+1. **Review requirements.** Read `requirements.md` (or its summary if one exists). Identify the key technical challenges. When requirements carry `AC-n` IDs, note in each design section which criteria it addresses — that linkage is what reviewers and the testing phase trace against.
 2. **Consult the knowledge graph.** If the project has a knowledge graph (`.aidlc/knowledge/` exists), run `aidlc knowledge context --scope phase --phase design` for existing architecture, decisions, and conventions before re-deriving them from code.
 3. **Define architecture.** Describe the high-level structure: components, their responsibilities, and how they communicate.
 4. **Specify interfaces.** For each component boundary, define the contract (function signatures, API shapes, data types).

package/skills/50-testing.md

@@ -27,11 +27,17 @@ Verify that the implementation satisfies all acceptance criteria. Produce eviden
    - Unit tests for pure logic and edge cases
    - Integration tests for component interactions
    - Property-based tests where inputs have broad domains
+   - **Reference AC IDs.** When `requirements.md` defines `AC-n` criteria, each test names the criteria it verifies — in the test name or a comment (e.g. `// AC-3`). The testing-phase gate scans test files for these references and fails on any active criterion with none. If two instances define the same ID, qualify the reference as `<instance>/AC-n`.
 3. **Run tests.** Execute the project's test suite. All new tests must pass.
 4. **Document results.** Write `testing.md` with:
    - Test plan (what was tested and why)
    - Results (pass/fail counts, any notable findings)
    - Coverage notes (which criteria are covered, any gaps)
+   - **`ac-coverage` block for indirect coverage.** A criterion verified manually or outside scannable test files is claimed in a fenced code block whose info string is `ac-coverage`, one `AC-<n>: <evidence>` line per entry — the gate unions these with scanned references:
+
+     ```ac-coverage
+     AC-7: verified manually — see results table above
+     ```
 5. **Address failures.** If tests reveal bugs, fix the implementation. Do not skip or weaken tests to force a pass.
 
 ## Exit Criteria