@aisdlc/core 4.9.0 → 4.9.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.cjs +34 -2
- package/dist/index.cjs.map +1 -1
- package/dist/index.js +34 -2
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/dist/index.cjs
CHANGED
|
@@ -14354,7 +14354,8 @@ var SKILL_EXPECTED_TOOLS = {
|
|
|
14354
14354
|
"aisdlc-doctor-migrate": ["doctor", "migrate"],
|
|
14355
14355
|
"aisdlc-release-compliance": ["verify", "kpi_release", "report_dashboard"],
|
|
14356
14356
|
"aisdlc-security-sca-triage": ["verify_security", "verify_privacy", "verify_licenses"],
|
|
14357
|
-
"aisdlc-bdd-gherkin": ["sdd_check_fix", "verify_testing"]
|
|
14357
|
+
"aisdlc-bdd-gherkin": ["sdd_check_fix", "verify_testing"],
|
|
14358
|
+
"aisdlc-spot-audit": ["inspect_element"]
|
|
14358
14359
|
};
|
|
14359
14360
|
function readExecutedMcpTools(auditLogFile) {
|
|
14360
14361
|
const executed = /* @__PURE__ */ new Set();
|
|
@@ -19354,6 +19355,29 @@ When consolidating multiple increments in a single release or PR, apply **only o
|
|
|
19354
19355
|
1. Extract: \`npx aisdlc gherkin extract --all\`
|
|
19355
19356
|
2. Scaffold RED steps: \`npx aisdlc gherkin scaffold <feature-file> --lang <lang> --fallback\`
|
|
19356
19357
|
3. Verify sync: \`npx aisdlc verify gherkin\`
|
|
19358
|
+
`
|
|
19359
|
+
}
|
|
19360
|
+
],
|
|
19361
|
+
"aisdlc-spot-audit": [
|
|
19362
|
+
{
|
|
19363
|
+
filename: "polymorphic-audit-matrix.md",
|
|
19364
|
+
content: `# Polymorphic Element Audit & Adversarial Matrix
|
|
19365
|
+
|
|
19366
|
+
## Layer-to-Verifier & Owner Role Routing
|
|
19367
|
+
| Target Element / Layer | Deterministic Pre-Checks | \`agent-auditor\` Focus (Quality / YAGNI) | \`agent-adversary\` Focus (Red Team / PoC) | Return Handoff Owner Role |
|
|
19368
|
+
| :--- | :--- | :--- | :--- | :--- |
|
|
19369
|
+
| **Product** (\`UC-*\`, \`FR-*\`, \`QR-*\`, \`BR-*\`, \`JRN-*\`, \`ARCH-INTRO-*\`) | \` inspect_element\`, \`verify_schemas\`, \`verify_duplicates\`, \`verify_pdac\` | Ambiguity, missing Gherkin \`@nominal\`/\`@boundary\`/\`@invalid\`, anti-library-only MVP & CRUD completeness | Contradictory rules, unreachable states, logic traps, unhandled exception flows | \`agent-product-analyst\` (or \`agent-expert-user\`) |
|
|
19370
|
+
| **Cybersecurity** (\`ACT-THREAT-*\`, \`ABUSE-*\`, \`SEC-REQ-*\`) | \`inspect_element\`, \`verify_schemas\`, \`verify_pdac\` | STRIDE/OWASP ASVS completeness, Zero Trust enclave binding (\`SEC-ENC-*\`) | Bypass vectors, unmitigated abuse paths, missing \`@security @mitigation\` negative BDD | \`agent-threat-modeler\` |
|
|
19371
|
+
| **Privacy** (\`DATA-ASSET-*\`, \`PRIV-ROPA-*\`, \`PRIV-REQ-*\`) | \`inspect_element\`, \`verify_schemas\`, \`verify_privacy\` | LINDDUN / GDPR Art. 30 completeness, retention & erasure strategy, DPIA gate | PII leakage vectors in logs/LLM prompts, re-identification / linkability attacks | \`agent-privacy-officer\` |
|
|
19372
|
+
| **Architecture** (\`CMP-*\`, \`ADR-*\`, \`ARCH-DEP-*\`, \`SEC-ENC-*\`) | \`inspect_element\`, \`verify_schemas\`, \`verify_traceability\` | Hexagonal Ports & Adapters, YAGNI, Contract-First DTOs, persistent \`CMP-OBSERVABILITY\` | SPOFs, race conditions, cascading failures, resource exhaustion, enclave boundary bypass | \`agent-system-architect\` |
|
|
19373
|
+
| **Verification Suites** (\`tests/**\`, \`*.feature\`) | \`inspect_element\`, \`verify_testing\`, \`npx aisdlc verify gherkin\` | Deterministic Gherkin sync, Zero-Mock integration, per-interactive-element Happy/Sad/Boundary coverage | Conceptual mutation testing (proving how broken/empty production code passes tests green) | \`agent-qa-engineer\` |
|
|
19374
|
+
| **Source Code** (\`src/**\`, \`packages/**\`) | \`inspect_element\`, \`verify_quality\`, \`verify_security\`, \`verify_privacy\`, \`verify_licenses\` | CC <= 10, Cognitive <= 15, MI >= 50, Lines <= 40, SOLID/DRY, 1:1 unit & UI tests, 4 UI states, zero fake-wiring | Boundary/injection PoC breaks (SQLi, XSS, path traversal, prompt injection), race triggers, CVSS v3.1 scoring | \`agent-developer\` |
|
|
19375
|
+
| **CI/CD & Infra** (\`.github/workflows/**\`, \`Dockerfile*\`, \`scripts/**\`) | \`inspect_element\`, \`verify_security\`, \`verify_licenses\` | Non-invasion of \`src/\`, gate preservation, cross-workflow consistency, license compliance | Pipeline credential leakage, supply-chain/action injection, cold-start outage vectors | \`agent-devops\` |
|
|
19376
|
+
|
|
19377
|
+
## Finding Classifications & Guardrails
|
|
19378
|
+
- **\`agent-auditor\` Labels**: \`[BLOCKING_DEFECT]\`, \`[SIMPLIFICATION]\`, \`[ADVISORY]\`.
|
|
19379
|
+
- **\`agent-adversary\` Proof-of-Break**: (1) Target Entity ID & SHA-256, (2) Failure Scenario / Attack Vector, (3) Concrete PoC, (4) Expected Impact & CVSS v3.1 score.
|
|
19380
|
+
- **Non-Invasive & Anti-Ping-Pong**: Neither auditor nor adversary edits target files directly. Conclude with a canonical Workflow Handoff (\`templates/workflow/agent-handoff.template.md\`) bounded to at most 1 remediation round.
|
|
19357
19381
|
`
|
|
19358
19382
|
}
|
|
19359
19383
|
]
|
|
@@ -19741,7 +19765,7 @@ var LIFECYCLE_SKILL_TEMPLATES = [
|
|
|
19741
19765
|
description: "Interactive technical inspector and graph navigator across AI-SDLC requirements (FR-*, QR-*, SEC-REQ-*, PRIV-REQ-*), architecture components (CMP-*, ADR-*), SDD tasks (TSK-*, CHG-*), test suites, and source code files. Provides concise technical summaries, upstream/downstream traceability mappings, and selectable navigation loops.",
|
|
19742
19766
|
references: "[`process/06_spec_driven_development.md`](../../process/06_spec_driven_development.md), [`process/08_citation_contract_and_drift.md`](../../process/08_citation_contract_and_drift.md), and [`process/10_quality_management_and_release_gates.md`](../../process/10_quality_management_and_release_gates.md).",
|
|
19743
19767
|
globs: "specs/**, architecture/**, src/**, packages/**, tests/**",
|
|
19744
|
-
body: '## Purpose & Trigger\nUse this skill whenever a user or agent requests to **inspect, explain, trace, or navigate** any element of the system:\n- **Requirements & Product:** `UC-*`, `FR-*`, `QR-*`, `BR-*`, `BC-*`, `ABUSE-*`, `DATA-ASSET-*`, `PRIV-ROPA-*`, `ARCH-INTRO-*`.\n- **Architecture & Decisions:** `CMP-*`, `ADR-*`, `SEC-ENC-*`.\n- **SDD & Tasks:** `TSK-*`, `CHG-*`, `HOF-*`.\n- **Source Code Files:** `src/**/*.ts`, `packages/**/*.ts`, etc.\n- **Verification Suites:** `.feature` BDD files, unit/integration specs.\n\nThis skill provides **impact analysis, context comprehension, and interactive graph exploration** with zero guesswork.\n\n---\n\n## Interactive Execution Playbook\n\n### Step 1: Target Resolution\n1. Extract the target identifier or file path indicated by the user (e.g., `FR-001`, `CMP-CORE`, `src/auth/jwt.ts`, `TSK-001`).\n2. If no target was specified, prompt the user with common anchor options (e.g., primary Use Cases `UC-*`, Core Components `CMP-*`, or an open input).\n\n### Step 2: Deterministic Inspection Engine\nExecute the inspection via MCP or CLI:\n* **Primary (MCP Tool):**\n Invoke MCP tool `inspect_element`:\n ```json\n {\n "query": "<target-id-or-path>"\n }\n ```\n* **Fallback (CLI):**\n Run command:\n ```bash\n npx aisdlc inspect "<target-id-or-path>" --json\n ```\n\n---\n\n### Step 3: Complete Technical Report Delivery (MANDATORY FIRST)\n> [!IMPORTANT]\n> **CRITICAL UX DIRECTIVE (Report First, Question After):**\n> The agent MUST always render and deliver the complete, detailed technical report to the user in visible text **BEFORE** prompting for the next element. Never invoke a blocking dialog or selector on an empty turn without the user having the full inspection visible.\n\nThe rendered response MUST contain:\n1. **Header:** Artifact ID, Title, Type (`requirement`, `component`, `source-file`, `task`), Layer (`product`, `architecture`, `code`, `test`, `governance`), and Status (`COMPLIANT`, `ORPHAN`, `DRIFT`).\n2. **File Location:** Clickable markdown link to the file.\n3. **Technical Summary:** Concise explanation (2\u20134 sentences) of what the element does, its responsibilities, key interfaces, and consolidated evolutionary increments (`### Incremento (CHG-*)`). If a canonical requirement still shows boilerplate text despite completed changes in `specs/changes/`, run `sdd_integrate` with `all: true` (`npx aisdlc sdd integrate --all`) first so canonical requirements reflect the consolidated specification.\n4. **Upstream Relations (Derives from / Mitigates / Governed by):**\n - \u2197\uFE0F List all parent requirements, use cases, business rules, or decisions that justify this element.\n5. **Downstream Relations (Satisfied by / Implemented in / Verified by):**\n - \u2198\uFE0F List all components implementing it, tasks developing it, and test suites validating it.\n6. **Numbered Navigable Items:** Clear, numbered list of connected nodes with their ID, type, and relationship.\n\n---\n\n### Step 4: Subsequent Navigation Formulation & Selector\nOnce the technical report is fully constructed:\n1. Formulate the closing question inviting the user to continue navigating the graph.\n2. If using the interactive selector (`ask_question`), execute it **in conjunction with or immediately following the complete report text**:\n * **Question:** *"\xBFHacia qu\xE9 elemento conectado deseas continuar la exploraci\xF3n?"*\n * **Options:** Formatted list of related elements from `relatedItems`:\n - `(Recommended) <ID-1> (<Type-1> \u2014 <relation-1>)`\n - `<ID-2> (<Type-2> \u2014 <relation-2>)`\n - `<ID-N> (<Type-N> \u2014 <relation-N>)`\n - `Terminar exploraci\xF3n`\n3. **Navigation Loop:**\n - When the user selects or indicates an element (either via UI selector or plain text/number), repeat **Step 2** with the new selection.\n - If the user selects `Terminar exploraci\xF3n`, summarize the traversal journey and conclude.'
|
|
19768
|
+
body: '## Purpose & Trigger\nUse this skill whenever a user or agent requests to **inspect, explain, trace, or navigate** any element of the system:\n- **Requirements & Product:** `UC-*`, `FR-*`, `QR-*`, `BR-*`, `BC-*`, `ABUSE-*`, `DATA-ASSET-*`, `PRIV-ROPA-*`, `ARCH-INTRO-*`.\n- **Architecture & Decisions:** `CMP-*`, `ADR-*`, `SEC-ENC-*`.\n- **SDD & Tasks:** `TSK-*`, `CHG-*`, `HOF-*`.\n- **Source Code Files:** `src/**/*.ts`, `packages/**/*.ts`, etc.\n- **Verification Suites:** `.feature` BDD files, unit/integration specs.\n\nThis skill provides **impact analysis, context comprehension, and interactive graph exploration** with zero guesswork.\n\n---\n\n## Interactive Execution Playbook\n\n### Step 1: Target Resolution\n1. Extract the target identifier or file path indicated by the user (e.g., `FR-001`, `CMP-CORE`, `src/auth/jwt.ts`, `TSK-001`).\n2. If no target was specified, prompt the user with common anchor options (e.g., primary Use Cases `UC-*`, Core Components `CMP-*`, or an open input).\n\n### Step 2: Deterministic Inspection Engine\nExecute the inspection via MCP or CLI:\n* **Primary (MCP Tool):**\n Invoke MCP tool `inspect_element`:\n ```json\n {\n "query": "<target-id-or-path>"\n }\n ```\n* **Fallback (CLI):**\n Run command:\n ```bash\n npx aisdlc inspect "<target-id-or-path>" --json\n ```\n\n---\n\n### Step 3: Complete Technical Report Delivery (MANDATORY FIRST)\n> [!IMPORTANT]\n> **CRITICAL UX DIRECTIVE (Report First, Question After):**\n> The agent MUST always render and deliver the complete, detailed technical report to the user in visible text **BEFORE** prompting for the next element. Never invoke a blocking dialog or selector on an empty turn without the user having the full inspection visible.\n\nThe rendered response MUST contain:\n1. **Header:** Artifact ID, Title, Type (`requirement`, `component`, `source-file`, `task`), Layer (`product`, `architecture`, `code`, `test`, `governance`), and Status (`COMPLIANT`, `ORPHAN`, `DRIFT`).\n2. **File Location:** Clickable markdown link to the file.\n3. **Technical Summary:** Concise explanation (2\u20134 sentences) of what the element does, its responsibilities, key interfaces, and consolidated evolutionary increments (`### Incremento (CHG-*)`). If a canonical requirement still shows boilerplate text despite completed changes in `specs/changes/`, run `sdd_integrate` with `all: true` (`npx aisdlc sdd integrate --all`) first so canonical requirements reflect the consolidated specification.\n4. **Upstream Relations (Derives from / Mitigates / Governed by):**\n - \u2197\uFE0F List all parent requirements, use cases, business rules, or decisions that justify this element.\n5. **Downstream Relations (Satisfied by / Implemented in / Verified by):**\n - \u2198\uFE0F List all components implementing it, tasks developing it, and test suites validating it.\n6. **Numbered Navigable Items:** Clear, numbered list of connected nodes with their ID, type, and relationship.\n\n---\n\n### Step 4: Subsequent Navigation Formulation & Selector\nOnce the technical report is fully constructed:\n1. Formulate the closing question inviting the user to continue navigating the graph.\n2. If using the interactive selector (`ask_question`), execute it **in conjunction with or immediately following the complete report text**:\n * **Question:** *"\xBFHacia qu\xE9 elemento conectado deseas continuar la exploraci\xF3n?"*\n * **Options:** Formatted list of related elements from `relatedItems`:\n - `(Recommended) <ID-1> (<Type-1> \u2014 <relation-1>)`\n - `<ID-2> (<Type-2> \u2014 <relation-2>)`\n - `<ID-N> (<Type-N> \u2014 <relation-N>)`\n - `Auditar este elemento (<ID>) con agent-auditor + agent-adversary (Handoff \u2192 aisdlc-spot-audit)`\n - `Terminar exploraci\xF3n`\n3. **Navigation & Audit Handoff Loop:**\n - When the user selects or indicates an element (either via UI selector or plain text/number), repeat **Step 2** with the new selection.\n - If the user selects `Auditar este elemento (<ID>) con agent-auditor + agent-adversary (Handoff \u2192 aisdlc-spot-audit)`, emit a Workflow Handoff transitioning directly into [`aisdlc-spot-audit`](../aisdlc-spot-audit/SKILL.md) targeting `<ID>`.\n - If the user selects `Terminar exploraci\xF3n`, summarize the traversal journey and conclude.'
|
|
19745
19769
|
},
|
|
19746
19770
|
{
|
|
19747
19771
|
id: "aisdlc-doctor-migrate",
|
|
@@ -19774,6 +19798,14 @@ var LIFECYCLE_SKILL_TEMPLATES = [
|
|
|
19774
19798
|
references: "[`process/06_spec_driven_development.md`](../../process/06_spec_driven_development.md) and [`process/10_quality_management_and_release_gates.md`](../../process/10_quality_management_and_release_gates.md).",
|
|
19775
19799
|
globs: "tests/features/**, tests/steps/**, specs/**",
|
|
19776
19800
|
body: "## Purpose & Trigger\nUse this skill whenever **authoring BDD acceptance criteria, extracting `.feature` files, or scaffolding RED step definitions** in TypeScript, Python, Go, Rust, or C#.\n\n## End-to-End Execution Playbook\n\n### Step 1: Author Gherkin Inside Markdown Specs\n1. Never create or edit `tests/features/*.feature` files manually.\n2. Author ```gherkin blocks inside `FR-*`, `SEC-REQ-*`, `PRIV-REQ-*`, or `specs/changes/active/<chg-id>/spec.md` with tags `@<ID> @automated @regression` and `@nominal`, `@boundary`, `@invalid` scenarios.\n\n### Step 2: Deterministic Extraction & Polyglot Step Scaffolding\n1. Run `npx aisdlc gherkin extract --all` (or `npx aisdlc check --fix`) to generate `tests/features/*.feature` deterministically.\n2. Scaffold failing RED step definitions in `tests/steps/` via:\n `npx aisdlc gherkin scaffold <feature-file> --lang <ts|py|go|rs|cs> --fallback`\n (omit `--fallback` when the native BDD generator is installed).\n3. Implement real failing assertions inside the scaffolded step files.\n\n### Step 3: Synchronization Gate\n1. Run `npx aisdlc verify gherkin` and `npx aisdlc verify testing` to confirm 100% Markdown-to-`.feature` parity and scenario coverage."
|
|
19801
|
+
},
|
|
19802
|
+
{
|
|
19803
|
+
id: "aisdlc-spot-audit",
|
|
19804
|
+
title: "360\xB0 Polymorphic Element Auditor & Adversarial Stress Playbook",
|
|
19805
|
+
description: "Audit any system element on demand \u2014 product specs (UC-*, FR-*, QR-*, BR-*), security/privacy artifacts (ABUSE-*, SEC-REQ-*, DATA-ASSET-*, PRIV-REQ-*), architecture components (CMP-*, ADR-*), SDD tasks (CHG-*, TSK-*), test suites, or source code files \u2014 by combining deterministic graph inspection (inspect_element) with parallel isolated evaluations by agent-auditor and agent-adversary and emitting a canonical Workflow Handoff.",
|
|
19806
|
+
references: "[`process/01_governance_and_roles.md`](../../process/01_governance_and_roles.md), [`process/09_agent_protocols.md`](../../process/09_agent_protocols.md), [`process/10_quality_management_and_release_gates.md`](../../process/10_quality_management_and_release_gates.md), and [`templates/workflow/agent-handoff.template.md`](../../templates/workflow/agent-handoff.template.md).",
|
|
19807
|
+
globs: "specs/**, architecture/**, security/**, privacy/**, src/**, packages/**, tests/**",
|
|
19808
|
+
body: '## Purpose & Trigger\nUse this skill whenever a user or upstream workflow (including a handoff from [`aisdlc-inspector`](../aisdlc-inspector/SKILL.md)) requests to **audit, stress-test, red-team, or challenge any single element or set of elements** on demand without running a full SDD lifecycle:\n- **Product & Vision:** `ARCH-INTRO-*`, `ACT-*`, `JRN-*`, `UC-*`, `FR-*`, `QR-*`, `BR-*`.\n- **Cybersecurity & Privacy:** `ACT-THREAT-*`, `ABUSE-*`, `SEC-REQ-*`, `DATA-ASSET-*`, `PRIV-ROPA-*`, `PRIV-REQ-*`.\n- **Architecture & Decisions:** `CMP-*`, `ADR-*`, `ARCH-DEP-*`, `SEC-ENC-*`.\n- **SDD Changes & Tasks:** `CHG-*`, `HOF-*`, `TSK-*`.\n- **Source Code & Infrastructure:** `src/**/*`, `packages/**/*`, `.github/workflows/*.yml`, `Dockerfile*`.\n- **Verification Suites:** `tests/**/*.spec.*`, `tests/features/*.feature`, `tests/steps/*`.\n\n---\n\n## End-to-End Execution Playbook\n\n### Step 1: Target Resolution & 360\xB0 Context Hydration (`inspect_element`)\n1. Extract the target identifier or file path indicated by the user (e.g., `UC-001`, `FR-002`, `CMP-CORE`, `src/auth/jwt.ts`, `tests/unit/auth.spec.ts`). If none was provided, prompt via `ask_question` with primary Use Cases (`UC-*`), Core Components (`CMP-*`), or active SDD changes (`CHG-*`).\n2. Run MCP tool `inspect_element` (`{"query": "<target-id-or-path>"}`) or CLI `npx aisdlc inspect "<target-id-or-path>" --json` to hydrate:\n - Canonical ID, layer (`product`, `architecture`, `security`, `privacy`, `code`, `test`, `governance`), file path, and Unix LF SHA-256 citation digest.\n - Traceability status (`COMPLIANT`, `ORPHAN`, `DRIFT`) and immediate upstream (\u2197\uFE0F) and downstream (\u2198\uFE0F) neighbors.\n3. Read the target file and its directly connected artifacts from disk.\n\n### Step 2: Layer-Specific Deterministic Pre-Audit Gates\nExecute deterministic verifiers matching the element\'s layer before invoking specialist subagents:\n- **Product / Security / Privacy / Architecture Specs:** Run `verify_schemas`, `verify_pdac`, and `verify_duplicates` (plus `verify_privacy` for `DATA-ASSET-*` / `PRIV-*`).\n- **Source Code (`src/**`, `packages/**`):** Run `verify_quality` (`quality-policy.yaml` AST metrics), `verify_security` (secrets & SAST), `verify_privacy` (PII leaks), and `verify_licenses`.\n- **Verification Suites (`tests/**`, `*.feature`):** Run `npx aisdlc verify gherkin` and `verify_testing`.\n- **SDD Changes & Tasks (`CHG-*`, `TSK-*`):** Run `verify_governance`, `verify_friction`, and `verify_traceability`.\n\n### Step 3: Concurrent Polymorphic Subagent Evaluation (`agent-auditor` $\\parallel$ `agent-adversary`)\n> [!IMPORTANT]\n> **MANDATORY CLEAN CONTEXT WINDOW ISOLATION (Commandment #6):**\n> Never role-play `agent-auditor` and `agent-adversary` inside the same context window. In subagent-capable IDEs (Antigravity `invoke_subagent`, Claude Code `Task`, Copilot `@agent-*`), spawn two isolated subagents in parallel passing the target file path, SHA-256 digest, and upstream/downstream context from Steps 1\u20132.\n\n1. **Branch A \u2014 [`agent-auditor`](../agent-auditor/SKILL.md) (Constructive Quality, YAGNI & Compliance Audit):**\n - **Product (`UC-*`, `FR-*`, `BR-*`):** Check for ambiguity, missing `@nominal`/`@boundary`/`@invalid` Gherkin scenarios, and enforce End-to-End MVP Completeness (rejecting library-only MVPs when human actors `ACT-*` exist, verifying UI modality and master-data CRUD prerequisites).\n - **Architecture (`CMP-*`, `ADR-*`):** Enforce Hexagonal Architecture (Ports & Adapters), YAGNI, Contract-First shared schemas, and persistent `CMP-OBSERVABILITY` (`OBS_STORAGE_PATH`, `flush()`, `ITelemetryExporter`).\n - **Source Code (`src/**`):** Enforce `quality-policy.yaml` thresholds ($CC \\le 10$, $Cognitive \\le 15$, $MI \\ge 50$, $Lines \\le 40$), SOLID/DRY, 1:1 method unit test (`tests/unit/`) and UI component test (`tests/e2e/` or `tests/ui/`) coverage, zero fake-wiring, all 4 UI states (`Loading`, `Empty`, `Error`, `Nominal`), modern visual aesthetics (Bootstrap 5 / modern Desktop / rich ANSI Console), and SPDX license compliance.\n - **Tests (`tests/**`):** Verify deterministic Gherkin extraction/scaffolding and per-interactive-element Happy/Sad/Boundary coverage.\n - **Classification:** Label every finding as `[BLOCKING_DEFECT]`, `[SIMPLIFICATION]`, or `[ADVISORY]`.\n\n2. **Branch B \u2014 [`agent-adversary`](../agent-adversary/SKILL.md) (Red Team, Chaos & Proof-of-Break Audit):**\n - **Product (`UC-*`, `FR-*`, `BR-*`):** Uncover contradictory business rules, unreachable states, logic traps, and unmodeled abuse paths.\n - **Architecture (`CMP-*`, `ADR-*`):** Simulate race conditions, cascading failures, resource exhaustion, Single Points of Failure (SPOFs), and enclave boundary bypasses.\n - **Tests (`tests/**`):** Perform **Conceptual Mutation Testing** \u2014 provide concrete mutant production code showing how a broken or empty implementation would falsely pass the test suite green.\n - **Source Code & Security (`src/**`, `SEC-REQ-*`):** Attack boundary inputs, concurrency races, memory/type edge breaks, injection vectors (SQLi, XSS, command, path traversal, prompt injection), secret/PII leaks, and auth bypasses with **CVSS v3.1** scoring.\n - **Mandatory 4-Part Proof-of-Break:** Every adversarial finding MUST include: *(1) Target Entity ID & SHA-256*, *(2) Failure Scenario / Attack Vector*, *(3) Concrete Reproducible PoC (input payload, sequence breakdown, or mutant code)*, and *(4) Expected Impact & CVSS v3.1 score*.\n\n### Step 4: Consolidated Audit Report & Canonical Workflow Handoff\n> [!IMPORTANT]\n> **CRITICAL UX DIRECTIVE (Report First, Handoff & Selector After):**\n> Always render the complete Consolidated Audit Report in visible text **BEFORE** presenting the interactive follow-up selector.\n\n1. **Render the Consolidated Audit Report:**\n - **1. Audited Target Header:** Artifact ID / Path, Layer, Traceability Status (`COMPLIANT` / `ORPHAN` / `DRIFT`), and Unix LF SHA-256 digest.\n - **2. Deterministic Gate Summary:** Pass/Fail status of Step 2 verifiers.\n - **3. `agent-auditor` Findings Matrix:** Grouped by `[BLOCKING_DEFECT]`, `[SIMPLIFICATION]`, and `[ADVISORY]`.\n - **4. `agent-adversary` Proof-of-Break Matrix:** Findings with Attack Vector, Concrete PoC, and CVSS v3.1 severity.\n - **5. Overall Audit Verdict:** `\u2705 PASS` (0 blocking defects, 0 Critical/High PoC breaks), `\u26A0\uFE0F PASS_WITH_ADVISORIES` (only simplifications/advisories), or `\u274C BLOCKED` ($ge 1$ `[BLOCKING_DEFECT]` or Critical/High PoC break).\n\n2. **Emit Canonical Workflow Handoff Block (`templates/workflow/agent-handoff.template.md`):**\n Emit the `### \u{1F504} Workflow Handoff` section routing remediation to the target element\'s responsible owner agent (bounded by the **Anti-Ping-Pong Guardrail**: maximum 1 remediation return round):\n - `UC-*` / `FR-*` / `QR-*` / `BR-*` / `JRN-*` $\\rightarrow$ `agent-product-analyst` (or `agent-expert-user`)\n - `ACT-THREAT-*` / `ABUSE-*` / `SEC-REQ-*` $\\rightarrow$ `agent-threat-modeler`\n - `DATA-ASSET-*` / `PRIV-ROPA-*` / `PRIV-REQ-*` $\\rightarrow$ `agent-privacy-officer`\n - `CMP-*` / `ADR-*` / `ARCH-DEP-*` $\\rightarrow$ `agent-system-architect`\n - `tests/**` / `*.feature` $\\rightarrow$ `agent-qa-engineer`\n - `src/**` / `packages/**` $\\rightarrow$ `agent-developer`\n - `.github/workflows/**` / `Dockerfile*` / `scripts/**` $\\rightarrow$ `agent-devops`\n\n3. **Interactive Handoff & Navigation Selector (`ask_question`):**\n Offer the user the next action via `ask_question`:\n - `(Recommended) Ejecutar Handoff de remediaci\xF3n con <owner-agent> (corregir hallazgos detectados)` (or `(Recommended) Volver a aisdlc-inspector para explorar nodos conectados` if verdict is `\u2705 PASS`)\n - `Abrir incremento gobernado SDD (Handoff \u2192 aisdlc-increment)`\n - `Auditar un elemento conectado (<related-ID-1>, <related-ID-2>, ...)`\n - `Inspeccionar grafo 360\xB0 del elemento (Handoff \u2192 aisdlc-inspector)`\n - `Finalizar auditor\xEDa`\n\n## Non-Negotiable Guardrails\n- **Strict Non-Invasion:** Neither `aisdlc-spot-audit`, `agent-auditor`, nor `agent-adversary` may directly edit or patch the audited files during the audit turn. All modifications happen after the human approves the remediation Handoff to the owner specialist agent.\n- **Zero Abstract Criticism:** Every adversarial finding without a concrete PoC and every quality finding without a specific line/section citation must be discarded before rendering the report.'
|
|
19777
19809
|
}
|
|
19778
19810
|
];
|
|
19779
19811
|
function formatSkillReferencesSection(skillId) {
|