[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BZGR7HBGKZTP8C7A3S90MV":3,"skill-same:01M7BZGR7HBGKZTP8C7A3S90MV":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7BZGR7HBGKZTP8C7A3S90MV","analysis-pipeline",null,"Reverse engineering - multi-source product intelligence analysis with provenance tracking. Master methodology for all analysis agents.","zak-keown\u002Fmoe","zak-keown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F320717241?v=4","01M7BZFXME0NW6TQX0H7AZM2KS","01M7BZFXN32VR0JN5AATRD53H4",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fpackages\u002Fbackstory\u002Fskills\u002Fanalysis-pipeline\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analysis-pipeline\ndescription: Reverse engineering - multi-source product intelligence analysis with provenance tracking. Master methodology for all analysis agents.\n---\n\n# Reverse Engineering\n\nYou analyze targets from multiple perspectives. You output behavioral specifications with provenance.\n\n## The Core Principle\n\n**Analyze deeply. Output behaviorally. Track provenance. Analyze COMPLETELY.**\n\n- **Analysis:** Tear apart the source\u002Fbinary\u002Fruntime. Trace every code path. Understand every decision tree.\n- **Output:** Write specs using behavioral language. No source identifiers in the output.\n- **Provenance:** Every behavioral claim cites its evidence source with `\u003C!-- cite: -->` annotations.\n- **Completeness:** Analyze ALL modules (P0, P1, P2, P3 - everything). Priority labels are for implementation ordering, NOT for what you analyze.\n\n## Exhaustive Reading (CRITICAL)\n\n**You MUST read every single line of code. You MUST identify every single routine.**\n\n- Do NOT skim code. Do NOT skip \"unimportant\" sections.\n- Do NOT rely on grep patterns alone - READ the actual source.\n- Every function, every method, every class, every module must be identified and understood.\n- If you haven't read a line, you don't know what it does.\n\n## The 7-Layer Pipeline\n\n```dot\ndigraph pipeline {\n    rankdir=TB;\n\n    \"Start analysis\" [shape=doublecircle];\n    \"Layer 1: Gather intelligence\" [shape=box];\n    \"Layer 2: Synthesize and map modules\" [shape=box];\n    \"Layer 3: Write deep behavioral specs\" [shape=box];\n    \"Gate 1: Verification passed?\" [shape=diamond];\n    \"Gate 1b: Source-to-spec completeness\" [shape=diamond];\n    \"Layer 4: Generate test vectors and acceptance criteria\" [shape=box];\n    \"Gate 2: Spec review passed?\" [shape=diamond];\n    \"Layer 5: Sanitize raw specs to output\u002F\" [shape=box];\n    \"Layer 6: Second-pass review passed?\" [shape=diamond];\n    \"Layer 7: Fidelity validation passed?\" [shape=diamond];\n    \"Analysis complete\" [shape=doublecircle];\n    \"Remediate Gate 1 findings\" [shape=box];\n    \"Remediate Gate 2 findings\" [shape=box];\n    \"Remediate Layer 6 findings\" [shape=box];\n    \"Remediate Layer 7 findings\" [shape=box];\n    \"STOP: Gate 1 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n    \"STOP: Gate 2 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n    \"STOP: Layer 6 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n    \"STOP: Layer 7 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n\n    \"Start analysis\" -> \"Layer 1: Gather intelligence\";\n    \"Layer 1: Gather intelligence\" -> \"Layer 2: Synthesize and map modules\";\n    \"Layer 2: Synthesize and map modules\" -> \"Layer 3: Write deep behavioral specs\";\n    \"Layer 3: Write deep behavioral specs\" -> \"Gate 1: Verification passed?\";\n    \"Gate 1: Verification passed?\" -> \"Gate 1b: Source-to-spec completeness\" [label=\"yes\"];\n    \"Gate 1: Verification passed?\" -> \"Remediate Gate 1 findings\" [label=\"no\"];\n    \"Remediate Gate 1 findings\" -> \"Gate 1: Verification passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Gate 1 findings\" -> \"STOP: Gate 1 failed after 3 attempts\" [label=\"attempt >= 3\"];\n    \"Gate 1b: Source-to-spec completeness\" -> \"Layer 4: Generate test vectors and acceptance criteria\" [label=\"pass\"];\n    \"Gate 1b: Source-to-spec completeness\" -> \"Remediate Gate 1 findings\" [label=\"gaps found\"];\n    \"Layer 4: Generate test vectors and acceptance criteria\" -> \"Gate 2: Spec review passed?\";\n    \"Gate 2: Spec review passed?\" -> \"Layer 5: Sanitize raw specs to output\u002F\" [label=\"yes\"];\n    \"Gate 2: Spec review passed?\" -> \"Remediate Gate 2 findings\" [label=\"no\"];\n    \"Remediate Gate 2 findings\" -> \"Gate 2: Spec review passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Gate 2 findings\" -> \"STOP: Gate 2 failed after 3 attempts\" [label=\"attempt >= 3\"];\n    \"Layer 5: Sanitize raw specs to output\u002F\" -> \"Layer 6: Second-pass review passed?\";\n    \"Layer 6: Second-pass review passed?\" -> \"Layer 7: Fidelity validation passed?\" [label=\"yes\"];\n    \"Layer 6: Second-pass review passed?\" -> \"Remediate Layer 6 findings\" [label=\"no\"];\n    \"Remediate Layer 6 findings\" -> \"Layer 6: Second-pass review passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Layer 6 findings\" -> \"STOP: Layer 6 failed after 3 attempts\" [label=\"attempt >= 3\"];\n    \"Layer 7: Fidelity validation passed?\" -> \"Analysis complete\" [label=\"yes\"];\n    \"Layer 7: Fidelity validation passed?\" -> \"Remediate Layer 7 findings\" [label=\"no\"];\n    \"Remediate Layer 7 findings\" -> \"Layer 7: Fidelity validation passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Layer 7 findings\" -> \"STOP: Layer 7 failed after 3 attempts\" [label=\"attempt >= 3\"];\n}\n```\n\n## Intelligence Sources\n\nLayer 1 auto-discovers available intelligence sources and consumes all of them by default:\n\n| Source Type | Agent Roles | Output Location | Origin |\n|------------|------------|----------------|-------------|\n| Source Code | bundle-splitter, chunk-analyzer, function-analyzer | workspace\u002Fraw\u002Fsource\u002F | RAW |\n| Decompiled Binaries | decompiler → chunk-analyzer | workspace\u002Fraw\u002Fsource\u002Fdecompiled\u002F | RAW |\n| Public Docs | doc-researcher | workspace\u002Fpublic\u002Fdocs\u002F | PUBLIC |\n| SDK\u002FEcosystem | sdk-analyzer, integration-test-miner | workspace\u002Fpublic\u002Fecosystem\u002F | PUBLIC |\n| Community | community-analyst | workspace\u002Fpublic\u002Fcommunity\u002F | PUBLIC |\n| Runtime Observation | cli-explorer, web-ui-explorer, behavior-observer, ux-documenter | workspace\u002Fraw\u002Fruntime\u002F | RAW |\n| Visual Exploration | visual-explorer | workspace\u002Fraw\u002Fruntime\u002Fvisual\u002F | RAW |\n| Binary Analysis | binary-surveyor, binary-deep-analyzer | workspace\u002Fraw\u002Fbinary\u002F | RAW |\n| Git History | git-archaeologist | workspace\u002Fraw\u002Fproject-history\u002F | RAW |\n| Test Suites | test-reader, test-runner | workspace\u002Fraw\u002Ftest-evidence\u002F | RAW |\n| Machine-Readable Contracts | contract-parser | workspace\u002Fpublic\u002Fcontracts\u002F | PUBLIC |\n\nSources are auto-discovered. Use `--exclude` to skip specific source types.\n\nSources are excluded only by `--exclude` flag or user request during discovery negotiation.\n\n## Source Coverage\n\nMore independent source types covering the same behaviors = higher-confidence specs.\n\n**Minimum for high-confidence:** 2+ independent source types covering the same behaviors. When a behavioral claim is supported by only one source, it gets `confidence=inferred` at best. When 2+ independent sources agree, it gets `confidence=confirmed`.\n\n## Provenance\n\nEvery behavioral claim MUST have a provenance citation:\n\n```markdown\nSessions expire after 30 minutes of inactivity.\n\u003C!-- cite: source=source-code, ref=workspace\u002Fraw\u002Fsource\u002Fanalysis\u002Fchunk-0046.md:23, confidence=confirmed, agent=deep-dive-analyzer, corroborated_by=runtime-observation -->\n```\n\n**Confidence levels:**\n- `confirmed` — 2+ independent sources agree\n- `inferred` — single source, direct evidence\n- `assumed` — reasoning from indirect evidence\n\nReference the **provenance-methodology** skill for complete format details.\n\n## Quality Gates\n\n### Gate 1 (after Layer 3 — behavioral specs)\n\n- **No contradictions** between specs — if two specs disagree, resolve before proceeding\n- **Constants and crypto verified** — exact values confirmed against source, not assumed\n- **Claims have provenance** — every behavioral claim cites its evidence source\n- **Assumed claims are the minority** — most claims should be confirmed or inferred from direct evidence. A module dominated by assumed claims needs more intelligence gathering\n- **All modules have specs** — completeness is forced, not optional\n\n### Gate 2 (after Layer 4 — test vectors and acceptance criteria)\n\n- **No implementation leakage** — specs describe behavior, not code structure\n- **No P0 completeness gaps** — critical behaviors are fully specified\n- **ACs have valid IDs and link to specs** — traceability is intact\n- **P0 ACs have test vectors** — critical acceptance criteria are testable\n- **No contamination in validation artifacts** — ACs and test vectors are clean\n\n## Mandatory Test Vectors\n\nLayer 4 (test vector generation) is NOT optional. Test vectors are the bridge between \"spec describes it\" and \"implementer actually builds it.\"\n\n```dot\ndigraph test_vectors {\n    rankdir=TB;\n\n    \"Layer 3 specs complete\" [shape=doublecircle];\n    \"Generate test vectors for P0 claims\" [shape=box];\n    \"Generate edge case vectors\" [shape=box];\n    \"Generate dependency contract vectors\" [shape=box];\n    \"All P0 behaviors have vectors?\" [shape=diamond];\n    \"Gate 1.5 PASS\" [shape=doublecircle];\n    \"STOP: Add missing vectors\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n\n    \"Layer 3 specs complete\" -> \"Generate test vectors for P0 claims\";\n    \"Generate test vectors for P0 claims\" -> \"Generate edge case vectors\";\n    \"Generate edge case vectors\" -> \"Generate dependency contract vectors\";\n    \"Generate dependency contract vectors\" -> \"All P0 behaviors have vectors?\";\n    \"All P0 behaviors have vectors?\" -> \"Gate 1.5 PASS\" [label=\"yes\"];\n    \"All P0 behaviors have vectors?\" -> \"STOP: Add missing vectors\" [label=\"no\"];\n}\n```\n\n### Test Vector Format\n\nEach vector follows Given\u002FWhen\u002FThen:\n\n```markdown\n### TV-LOADER-001: TypeScript file execution\nGIVEN: A file `test.ts` containing `interface Foo { x: number }; console.log(\"ok\")`\nWHEN: Run through tsx\nTHEN: Output is \"ok\", exit code 0\n\n### TV-LOADER-002: JSON import without explicit attribute\nGIVEN: A file importing `.\u002Fdata.json` without `with { type: 'json' }`\nWHEN: Run through tsx on Node >= 18.19\nTHEN: Import succeeds (hook auto-adds the attribute)\n\n### TV-LOADER-003: Invalid custom tsconfig\nGIVEN: `--tsconfig nonexistent.json` flag specified\nWHEN: Run through tsx\nTHEN: Error reported, non-zero exit code\n```\n\n### What Needs Vectors\n\n- Every P0 behavioral claim\n- Every documented edge case\n- Every dependency API contract failure mode\n- Every Node.js version-dependent behavior\n\n## Workspace Structure\n\n```\nworkspace\u002F\n├── public\u002F                    # Public origin\n│   ├── docs\u002F                  # doc-researcher output\n│   ├── ecosystem\u002F             # sdk-analyzer output\n│   └── contracts\u002F             # contract-parser output\n├── raw\u002F                   # RAW - requires sanitization\n│   ├── source\u002F                # Source code analysis\n│   │   ├── chunks\u002F\n│   │   ├── analysis\u002F\n│   │   ├── functions\u002F\n│   │   ├── manifests\u002F\n│   │   └── exploration\u002F\n│   ├── runtime\u002F               # Runtime observation\n│   │   ├── cli\u002F\n│   │   ├── web\u002F\n│   │   ├── behaviors\u002F\n│   │   ├── ux-flows\u002F\n│   │   └── visual\u002F            # visual-explorer output\n│   ├── binary\u002F                # Binary analysis\n│   ├── project-history\u002F       # git-archaeologist output\n│   ├── test-evidence\u002F         # test-reader, test-runner output\n│   ├── synthesis\u002F             # Layer 2 output\n│   │   ├── features\u002F\n│   │   ├── architecture\u002F\n│   │   ├── api\u002F\n│   │   ├── behavioral-summaries\u002F\n│   │   └── module-map.md\n│   └── specs\u002F                 # Layer 3\u002F4 output\n│       ├── modules\u002F\n│       ├── journeys\u002F\n│       ├── contracts\u002F\n│       ├── test-vectors\u002F\n│       └── validation\u002F\n├── output\u002F                     # Sanitized specs\n│   └── specs\u002F\n├── provenance\u002F                # Session logs\n│   └── sessions\u002F\n└── workspace.json             # Metadata\n```\n\n## What the Implementer Needs\n\n### 0. Complete Feature Inventory\n- **All CLI flags**: Including hidden\u002Fdebug ones\n- **All interactive commands**: Runtime commands with arguments\n- **All keyboard shortcuts**: Every shortcut and what it does\n- **All env vars and config keys**: Complete list\n\n### 1. External Contracts\n- CLI interface, environment variables, configuration files\n\n### 2. Wire Protocols\n- Request\u002Fresponse formats, wire format, error responses\n\n### 3. Observable Behaviors\n- State machines, decision logic, workflows, error handling\n\n### 4. Test Vectors + Acceptance Criteria\n- Input\u002Foutput pairs, error conditions, state transitions\n- Formal Given\u002FWhen\u002FThen acceptance criteria per module\n\n### 5. User-Visible Text\n- Error messages, prompts, status messages\n\n### 6. User Journeys\n- End-to-end flows from input to output\n\n## What IS vs ISN'T Contamination\n\n### PRESERVE (Behavioral Interfaces)\n\n| Type | Examples | Why |\n|------|----------|-----|\n| Environment variables | `DATABASE_URL`, `DEBUG` | External API |\n| CLI flags | `--format`, `--workers` | External API |\n| Config keys | `upstreams`, `log_level` | External API |\n| API fields | `request_id`, `batch_size` | Protocol spec |\n| User-facing paths | `~\u002F.app\u002Fconfig.toml` | Behavioral contract |\n| Protocol names | `SSE`, `gRPC`, `OAuth` | Behavioral contract |\n| Error messages | Exact text | UX contract |\n\n### REMOVE (Implementation Details)\n\n| Type | Examples | Why |\n|------|----------|-----|\n| Function names | `parseArgs()`, `handleRequest()` | Internal code |\n| Variable names | `requestId`, `configMap` | Internal code |\n| Minified identifiers | `sp`, `r0`, `Ab2()` | Internal code |\n| Line numbers | \"Line 1234\" | Internal code |\n| Source file paths | \"in src\u002Fcli.ts\" | Internal code |\n| Code structure | \"calls X then Y\" | Internal code |\n\n## Running Analysis\n\n```\n\u002Fanalyze [path]                              # Discover and consume everything\n\u002Fanalyze [path] --exclude source             # Black-box analysis\n\u002Fanalyze [path] --exclude git-history        # Skip commit mining\n```\n\n## After analysis completes\n\n1. Gates must PASS\n2. Run `\u002Fsanitize workspace\u002F` to produce output specs\n3. END SESSION — analysis is complete\n\n## Handoff to Implementation\n\nThe output specs in `workspace\u002Foutput\u002F` are the input for implementation. Backstory stops here. The implementation team reads:\n\n- `workspace\u002Foutput\u002Fspecs\u002F` — per-domain behavioral specs\n- `workspace\u002Foutput\u002Ftest-vectors\u002F` — concrete input\u002Foutput pairs to drive TDD\n- `workspace\u002Foutput\u002Fvalidation\u002Facceptance-criteria\u002F` — Given\u002FWhen\u002FThen acceptance criteria\n\nThe test vectors and acceptance criteria give the implementation pipeline a head start on proof obligations. How the implementation is carried out — walking skeletons, iteration planning, TDD cadence, review protocols — is outside Backstory's scope.\n\nBackstory's job is to produce specs good enough to implement from. Implementation is a separate concern with its own methodology.\n","# Reverse Engineering\n\nYou analyze targets from multiple perspectives. You output behavioral specifications with provenance.\n\n## The Core Principle\n\n**Analyze deeply. Output behaviorally. Track provenance. Analyze COMPLETELY.**\n\n- **Analysis:** Tear apart the source\u002Fbinary\u002Fruntime. Trace every code path. Understand every decision tree.\n- **Output:** Write specs using behavioral language. No source identifiers in the output.\n- **Provenance:** Every behavioral claim cites its evidence source with `\u003C!-- cite: -->` annotations.\n- **Completeness:** Analyze ALL modules (P0, P1, P2, P3 - everything). Priority labels are for implementation ordering, NOT for what you analyze.\n\n## Exhaustive Reading (CRITICAL)\n\n**You MUST read every single line of code. You MUST identify every single routine.**\n\n- Do NOT skim code. Do NOT skip \"unimportant\" sections.\n- Do NOT rely on grep patterns alone - READ the actual source.\n- Every function, every method, every class, every module must be identified and understood.\n- If you haven't read a line, you don't know what it does.\n\n## The 7-Layer Pipeline\n\n```dot\ndigraph pipeline {\n    rankdir=TB;\n\n    \"Start analysis\" [shape=doublecircle];\n    \"Layer 1: Gather intelligence\" [shape=box];\n    \"Layer 2: Synthesize and map modules\" [shape=box];\n    \"Layer 3: Write deep behavioral specs\" [shape=box];\n    \"Gate 1: Verification passed?\" [shape=diamond];\n    \"Gate 1b: Source-to-spec completeness\" [shape=diamond];\n    \"Layer 4: Generate test vectors and acceptance criteria\" [shape=box];\n    \"Gate 2: Spec review passed?\" [shape=diamond];\n    \"Layer 5: Sanitize raw specs to output\u002F\" [shape=box];\n    \"Layer 6: Second-pass review passed?\" [shape=diamond];\n    \"Layer 7: Fidelity validation passed?\" [shape=diamond];\n    \"Analysis complete\" [shape=doublecircle];\n    \"Remediate Gate 1 findings\" [shape=box];\n    \"Remediate Gate 2 findings\" [shape=box];\n    \"Remediate Layer 6 findings\" [shape=box];\n    \"Remediate Layer 7 findings\" [shape=box];\n    \"STOP: Gate 1 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n    \"STOP: Gate 2 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n    \"STOP: Layer 6 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n    \"STOP: Layer 7 failed after 3 attempts\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n\n    \"Start analysis\" -> \"Layer 1: Gather intelligence\";\n    \"Layer 1: Gather intelligence\" -> \"Layer 2: Synthesize and map modules\";\n    \"Layer 2: Synthesize and map modules\" -> \"Layer 3: Write deep behavioral specs\";\n    \"Layer 3: Write deep behavioral specs\" -> \"Gate 1: Verification passed?\";\n    \"Gate 1: Verification passed?\" -> \"Gate 1b: Source-to-spec completeness\" [label=\"yes\"];\n    \"Gate 1: Verification passed?\" -> \"Remediate Gate 1 findings\" [label=\"no\"];\n    \"Remediate Gate 1 findings\" -> \"Gate 1: Verification passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Gate 1 findings\" -> \"STOP: Gate 1 failed after 3 attempts\" [label=\"attempt >= 3\"];\n    \"Gate 1b: Source-to-spec completeness\" -> \"Layer 4: Generate test vectors and acceptance criteria\" [label=\"pass\"];\n    \"Gate 1b: Source-to-spec completeness\" -> \"Remediate Gate 1 findings\" [label=\"gaps found\"];\n    \"Layer 4: Generate test vectors and acceptance criteria\" -> \"Gate 2: Spec review passed?\";\n    \"Gate 2: Spec review passed?\" -> \"Layer 5: Sanitize raw specs to output\u002F\" [label=\"yes\"];\n    \"Gate 2: Spec review passed?\" -> \"Remediate Gate 2 findings\" [label=\"no\"];\n    \"Remediate Gate 2 findings\" -> \"Gate 2: Spec review passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Gate 2 findings\" -> \"STOP: Gate 2 failed after 3 attempts\" [label=\"attempt >= 3\"];\n    \"Layer 5: Sanitize raw specs to output\u002F\" -> \"Layer 6: Second-pass review passed?\";\n    \"Layer 6: Second-pass review passed?\" -> \"Layer 7: Fidelity validation passed?\" [label=\"yes\"];\n    \"Layer 6: Second-pass review passed?\" -> \"Remediate Layer 6 findings\" [label=\"no\"];\n    \"Remediate Layer 6 findings\" -> \"Layer 6: Second-pass review passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Layer 6 findings\" -> \"STOP: Layer 6 failed after 3 attempts\" [label=\"attempt >= 3\"];\n    \"Layer 7: Fidelity validation passed?\" -> \"Analysis complete\" [label=\"yes\"];\n    \"Layer 7: Fidelity validation passed?\" -> \"Remediate Layer 7 findings\" [label=\"no\"];\n    \"Remediate Layer 7 findings\" -> \"Layer 7: Fidelity validation passed?\" [label=\"attempt \u003C 3\"];\n    \"Remediate Layer 7 findings\" -> \"STOP: Layer 7 failed after 3 attempts\" [label=\"attempt >= 3\"];\n}\n```\n\n## Intelligence Sources\n\nLayer 1 auto-discovers available intelligence sources and consumes all of them by default:\n\n| Source Type | Agent Roles | Output Location | Origin |\n|------------|------------|----------------|-------------|\n| Source Code | bundle-splitter, chunk-analyzer, function-analyzer | workspace\u002Fraw\u002Fsource\u002F | RAW |\n| Decompiled Binaries | decompiler → chunk-analyzer | workspace\u002Fraw\u002Fsource\u002Fdecompiled\u002F | RAW |\n| Public Docs | doc-researcher | workspace\u002Fpublic\u002Fdocs\u002F | PUBLIC |\n| SDK\u002FEcosystem | sdk-analyzer, integration-test-miner | workspace\u002Fpublic\u002Fecosystem\u002F | PUBLIC |\n| Community | community-analyst | workspace\u002Fpublic\u002Fcommunity\u002F | PUBLIC |\n| Runtime Observation | cli-explorer, web-ui-explorer, behavior-observer, ux-documenter | workspace\u002Fraw\u002Fruntime\u002F | RAW |\n| Visual Exploration | visual-explorer | workspace\u002Fraw\u002Fruntime\u002Fvisual\u002F | RAW |\n| Binary Analysis | binary-surveyor, binary-deep-analyzer | workspace\u002Fraw\u002Fbinary\u002F | RAW |\n| Git History | git-archaeologist | workspace\u002Fraw\u002Fproject-history\u002F | RAW |\n| Test Suites | test-reader, test-runner | workspace\u002Fraw\u002Ftest-evidence\u002F | RAW |\n| Machine-Readable Contracts | contract-parser | workspace\u002Fpublic\u002Fcontracts\u002F | PUBLIC |\n\nSources are auto-discovered. Use `--exclude` to skip specific source types.\n\nSources are excluded only by `--exclude` flag or user request during discovery negotiation.\n\n## Source Coverage\n\nMore independent source types covering the same behaviors = higher-confidence specs.\n\n**Minimum for high-confidence:** 2+ independent source types covering the same behaviors. When a behavioral claim is supported by only one source, it gets `confidence=inferred` at best. When 2+ independent sources agree, it gets `confidence=confirmed`.\n\n## Provenance\n\nEvery behavioral claim MUST have a provenance citation:\n\n```markdown\nSessions expire after 30 minutes of inactivity.\n\u003C!-- cite: source=source-code, ref=workspace\u002Fraw\u002Fsource\u002Fanalysis\u002Fchunk-0046.md:23, confidence=confirmed, agent=deep-dive-analyzer, corroborated_by=runtime-observation -->\n```\n\n**Confidence levels:**\n- `confirmed` — 2+ independent sources agree\n- `inferred` — single source, direct evidence\n- `assumed` — reasoning from indirect evidence\n\nReference the **provenance-methodology** skill for complete format details.\n\n## Quality Gates\n\n### Gate 1 (after Layer 3 — behavioral specs)\n\n- **No contradictions** between specs — if two specs disagree, resolve before proceeding\n- **Constants and crypto verified** — exact values confirmed against source, not assumed\n- **Claims have provenance** — every behavioral claim cites its evidence source\n- **Assumed claims are the minority** — most claims should be confirmed or inferred from direct evidence. A module dominated by assumed claims needs more intelligence gathering\n- **All modules have specs** — completeness is forced, not optional\n\n### Gate 2 (after Layer 4 — test vectors and acceptance criteria)\n\n- **No implementation leakage** — specs describe behavior, not code structure\n- **No P0 completeness gaps** — critical behaviors are fully specified\n- **ACs have valid IDs and link to specs** — traceability is intact\n- **P0 ACs have test vectors** — critical acceptance criteria are testable\n- **No contamination in validation artifacts** — ACs and test vectors are clean\n\n## Mandatory Test Vectors\n\nLayer 4 (test vector generation) is NOT optional. Test vectors are the bridge between \"spec describes it\" and \"implementer actually builds it.\"\n\n```dot\ndigraph test_vectors {\n    rankdir=TB;\n\n    \"Layer 3 specs complete\" [shape=doublecircle];\n    \"Generate test vectors for P0 claims\" [shape=box];\n    \"Generate edge case vectors\" [shape=box];\n    \"Generate dependency contract vectors\" [shape=box];\n    \"All P0 behaviors have vectors?\" [shape=diamond];\n    \"Gate 1.5 PASS\" [shape=doublecircle];\n    \"STOP: Add missing vectors\" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];\n\n    \"Layer 3 specs complete\" -> \"Generate test vectors for P0 claims\";\n    \"Generate test vectors for P0 claims\" -> \"Generate edge case vectors\";\n    \"Generate edge case vectors\" -> \"Generate dependency contract vectors\";\n    \"Generate dependency contract vectors\" -> \"All P0 behaviors have vectors?\";\n    \"All P0 behaviors have vectors?\" -> \"Gate 1.5 PASS\" [label=\"yes\"];\n    \"All P0 behaviors have vectors?\" -> \"STOP: Add missing vectors\" [label=\"no\"];\n}\n```\n\n### Test Vector Format\n\nEach vector follows Given\u002FWhen\u002FThen:\n\n```markdown\n### TV-LOADER-001: TypeScript file execution\nGIVEN: A file `test.ts` containing `interface Foo { x: number }; console.log(\"ok\")`\nWHEN: Run through tsx\nTHEN: Output is \"ok\", exit code 0\n\n### TV-LOADER-002: JSON import without explicit attribute\nGIVEN: A file importing `.\u002Fdata.json` without `with { type: 'json' }`\nWHEN: Run through tsx on Node >= 18.19\nTHEN: Import succeeds (hook auto-adds the attribute)\n\n### TV-LOADER-003: Invalid custom tsconfig\nGIVEN: `--tsconfig nonexistent.json` flag specified\nWHEN: Run through tsx\nTHEN: Error reported, non-zero exit code\n```\n\n### What Needs Vectors\n\n- Every P0 behavioral claim\n- Every documented edge case\n- Every dependency API contract failure mode\n- Every Node.js version-dependent behavior\n\n## Workspace Structure\n\n```\nworkspace\u002F\n├── public\u002F                    # Public origin\n│   ├── docs\u002F                  # doc-researcher output\n│   ├── ecosystem\u002F             # sdk-analyzer output\n│   └── contracts\u002F             # contract-parser output\n├── raw\u002F                   # RAW - requires sanitization\n│   ├── source\u002F                # Source code analysis\n│   │   ├── chunks\u002F\n│   │   ├── analysis\u002F\n│   │   ├── functions\u002F\n│   │   ├── manifests\u002F\n│   │   └── exploration\u002F\n│   ├── runtime\u002F               # Runtime observation\n│   │   ├── cli\u002F\n│   │   ├── web\u002F\n│   │   ├── behaviors\u002F\n│   │   ├── ux-flows\u002F\n│   │   └── visual\u002F            # visual-explorer output\n│   ├── binary\u002F                # Binary analysis\n│   ├── project-history\u002F       # git-archaeologist output\n│   ├── test-evidence\u002F         # test-reader, test-runner output\n│   ├── synthesis\u002F             # Layer 2 output\n│   │   ├── features\u002F\n│   │   ├── architecture\u002F\n│   │   ├── api\u002F\n│   │   ├── behavioral-summaries\u002F\n│   │   └── module-map.md\n│   └── specs\u002F                 # Layer 3\u002F4 output\n│       ├── modules\u002F\n│       ├── journeys\u002F\n│       ├── contracts\u002F\n│       ├── test-vectors\u002F\n│       └── validation\u002F\n├── output\u002F                     # Sanitized specs\n│   └── specs\u002F\n├── provenance\u002F                # Session logs\n│   └── sessions\u002F\n└── workspace.json             # Metadata\n```\n\n## What the Implementer Needs\n\n### 0. Complete Feature Inventory\n- **All CLI flags**: Including hidden\u002Fdebug ones\n- **All interactive commands**: Runtime commands with arguments\n- **All keyboard shortcuts**: Every shortcut and what it does\n- **All env vars and config keys**: Complete list\n\n### 1. External Contracts\n- CLI interface, environment variables, configuration files\n\n### 2. Wire Protocols\n- Request\u002Fresponse formats, wire format, error responses\n\n### 3. Observable Behaviors\n- State machines, decision logic, workflows, error handling\n\n### 4. Test Vectors + Acceptance Criteria\n- Input\u002Foutput pairs, error conditions, state transitions\n- Formal Given\u002FWhen\u002FThen acceptance criteria per module\n\n### 5. User-Visible Text\n- Error messages, prompts, status messages\n\n### 6. User Journeys\n- End-to-end flows from input to output\n\n## What IS vs ISN'T Contamination\n\n### PRESERVE (Behavioral Interfaces)\n\n| Type | Examples | Why |\n|------|----------|-----|\n| Environment variables | `DATABASE_URL`, `DEBUG` | External API |\n| CLI flags | `--format`, `--workers` | External API |\n| Config keys | `upstreams`, `log_level` | External API |\n| API fields | `request_id`, `batch_size` | Protocol spec |\n| User-facing paths | `~\u002F.app\u002Fconfig.toml` | Behavioral contract |\n| Protocol names | `SSE`, `gRPC`, `OAuth` | Behavioral contract |\n| Error messages | Exact text | UX contract |\n\n### REMOVE (Implementation Details)\n\n| Type | Examples | Why |\n|------|----------|-----|\n| Function names | `parseArgs()`, `handleRequest()` | Internal code |\n| Variable names | `requestId`, `configMap` | Internal code |\n| Minified identifiers | `sp`, `r0`, `Ab2()` | Internal code |\n| Line numbers | \"Line 1234\" | Internal code |\n| Source file paths | \"in src\u002Fcli.ts\" | Internal code |\n| Code structure | \"calls X then Y\" | Internal code |\n\n## Running Analysis\n\n```\n\u002Fanalyze [path]                              # Discover and consume everything\n\u002Fanalyze [path] --exclude source             # Black-box analysis\n\u002Fanalyze [path] --exclude git-history        # Skip commit mining\n```\n\n## After analysis completes\n\n1. Gates must PASS\n2. Run `\u002Fsanitize workspace\u002F` to produce output specs\n3. END SESSION — analysis is complete\n\n## Handoff to Implementation\n\nThe output specs in `workspace\u002Foutput\u002F` are the input for implementation. Backstory stops here. The implementation team reads:\n\n- `workspace\u002Foutput\u002Fspecs\u002F` — per-domain behavioral specs\n- `workspace\u002Foutput\u002Ftest-vectors\u002F` — concrete input\u002Foutput pairs to drive TDD\n- `workspace\u002Foutput\u002Fvalidation\u002Facceptance-criteria\u002F` — Given\u002FWhen\u002FThen acceptance criteria\n\nThe test vectors and acceptance criteria give the implementation pipeline a head start on proof obligations. How the implementation is carried out — walking skeletons, iteration planning, TDD cadence, review protocols — is outside Backstory's scope.\n\nBackstory's job is to produce specs good enough to implement from. Implementation is a separate concern with its own methodology.\n",{"name":5,"description":7},"main","728894f3f85fbd4e788f015ddfd72bb6155d5dd5","packages\u002Fbackstory\u002Fskills\u002Fanalysis-pipeline",1,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe","https:\u002F\u002Fgithub.com\u002Fzak-keown","2026-09-05 06:29:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add zak-keown\u002Fmoe --skill analysis-pipeline",{"tool":36,"command":37},"bunx","bunx skills add zak-keown\u002Fmoe --skill analysis-pipeline",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zak-keown\u002Fmoe --skill analysis-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fpackages\u002Fbackstory\u002Fskills\u002Fanalysis-pipeline\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7C1Z5362Y8NVRZ69HWP0ZD0","write-skill","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7C1YZ9966WK9R6ZRPCGWF3G","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7C1YMR4SJD7BPBBPXZCVGVH","write-clearly","Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-clearly\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7C1YH9805YSM0N20VQAVSXF","windows-vm","Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwindows-vm\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7C1YD87SCNEJ2C9B8HFR2NQ","verify-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating MRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7C1YARDEHT0TJ9BRG30ZCF4","using-moe","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fusing-moe\u002FSKILL.md",[],[]]