[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DNFFZ8R658G09GEFKQJPEN":3,"skill-same:01M6DNFFZ8R658G09GEFKQJPEN":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6DNFFZ8R658G09GEFKQJPEN","aac-investigate",null,"Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.","msayedshokry\u002FAgileAgentCanvasExt","msayedshokry","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35009459?v=4","01M6DN5RZZ297CGWTNJ6ERZQ8W","Mohamed Sayed","01M6DN5S4XS7SVCSXZRW2XR0XF",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-investigate\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"investigate","aac investigate","code","investigation","model","trace","user","use","evidence","bug","build","incident","input","2026-11-10 10:12:30",false,"---\nname: aac-investigate\ndescription: Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.\n---\n\n# Investigate\n\n## Overview\n\nReconstruct what's happening, or what an unfamiliar area does, from the available evidence. Produce a structured case\nfile another engineer can pick up cold. Calibrate continuously between defect-chasing (symptom-driven) and\narea-exploration (no symptom); the same discipline applies on both ends.\n\n**Args:** A ticket ID, log file path, diagnostic archive, error message, code area name, problem description, or a path\nto an existing case file. The last form resumes a prior investigation; everything else opens a new case.\n\n**Output:** `{implementation_artifacts}\u002F{workflow.case_file_subdir}\u002F{workflow.case_file_filename}`. Reference inputs\nare recorded; raw content is not read into the parent context until an outcome calls for it.\n\n`{slug}` is the ticket ID when one is provided, otherwise a short descriptive name agreed with the user, sanitized to\nlowercase alphanumeric with hyphens. On collision with an existing case file at the resolved path, ask whether to\nrename to `slug-YYYY-MM-DD.md` or resume the existing file (resuming routes to Outcome 0).\n\nAfter every outcome, present what was learned and pause for the user before continuing.\n\n## Principles\n\n- **Evidence grading.**\n  - **Confirmed.** Directly observed; cite `path:line`, log timestamp, or commit hash.\n  - **Deduced.** Logically follows from Confirmed evidence; show the chain.\n  - **Hypothesized.** Plausible but unconfirmed; state what would confirm or refute it.\n- **Stronghold first.** Anchor in one Confirmed piece of evidence and expand outward. Never start from a theory and\n  hunt for support. When evidence is sparse, switch to evidence-light mode (Outcome 1 branch).\n- **Challenge the premise.** The user's description is a hypothesis, not a fact. Verify independently; if evidence\n  contradicts, say so.\n- **Follow the evidence, not the narrative.** When evidence contradicts the working theory, update the theory — never\n  the other way around. Resist confirmation bias even when the user is convinced.\n- **Hypotheses are never deleted.** Update Status (Open \u002F Confirmed \u002F Refuted) and add a Resolution. Wrong turns are\n  part of the deliverable.\n- **Missing evidence is itself a finding.** Document the gap, what it would resolve, and how to obtain it.\n- **Write it down early.** Initialize the case file as soon as the slug is agreed; it is the persistent state across\n  interruptions.\n- **Path:line citations** use CWD-relative format, no leading `\u002F`, so they're clickable in IDE-embedded terminals.\n- **Delegation discipline.** When a step requires reading 5+ files or any file >10K tokens, delegate to a subagent\n  that returns structured JSON only. Cite `path:line` from the result; don't re-read in the parent.\n- **Issue independent operations in parallel** (multi-grep, multi-read, parallel inventories) — one message, multiple\n  tool calls.\n- **Communication.** Evidence-first language (\"the evidence shows\", \"unconfirmed, requires X to verify\"). No hedging,\n  no narrative.\n\n## On Activation\n\n### Step 1: Resolve the workflow block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\nIf the script fails, stop and surface the error.\n\n### Step 2: Execute prepend steps\n\nRun each entry in `{workflow.activation_steps_prepend}` in order.\n\n### Step 3: Load persistent facts\n\nTreat each entry in `{workflow.persistent_facts}` as foundational context. `file:` prefixes are paths or globs under\n`{project-root}` (load contents); other entries are facts verbatim.\n\n### Step 4: Load config\n\nLoad `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve `{user_name}`, `{communication_language}`,\n`{document_output_language}`, `{implementation_artifacts}`, `{project_knowledge}`. If `{implementation_artifacts}` is\nunresolved, fall back to `.\u002Finvestigations\u002F` and surface the fallback before initializing.\n\n### Step 5: Greet\n\nGreet `{user_name}` in `{communication_language}`.\n\n### Step 6: Execute append steps\n\nRun each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.\n\n### Step 7: Acknowledge and route\n\nAcknowledge the input as a reference (record paths and IDs; don't read raw content). Path to an existing case file →\nOutcome 0. Otherwise → Outcome 1.\n\n## Procedure\n\n### Outcome 0: Existing case is loaded and surfaced\n\nRead the case file. Surface, in order: open hypotheses (Status = Open) with their confirm\u002Frefute criteria; open\nbacklog (Status ≠ Done); missing-evidence rows; last Conclusion with confidence. Ask which thread to pull. New\nevidence opens a new `## Follow-up: {YYYY-MM-DD}` block (append `#2`, `#3` on same-day reentry). Pause for user with the recap above; wait for direction.\n\n### Outcome 1: Scope and stronghold are established\n\nAcknowledge each input shape — record location, scope, time window only; bulk reads happen in Outcome 2.\n\n- **Issue tracker ticket.** Fetch full details via available MCP tools.\n- **Diagnostic archive.** Record path, file count, time window.\n- **Log file or stack trace.** Record path and time window; only the stack frame already in the user's message is in\n  scope here.\n- **Free-text description.** Capture verbatim; treat as hypothesis.\n- **Code area name** (no symptom). Record entry point.\n- **Recent commit area.** Record commit range.\n\nIf the user arrived with a hypothesis, register it as Hypothesis #1. Find the stronghold *independently*; the user's\nhypothesis is one of the things the stronghold validates or refutes.\n\nFind a stronghold: a Confirmed piece of evidence (error message, function name, HTTP route, config parameter, test\ncase). Anchor here.\n\n**Initialize `{case_file}` before branching.** The path is\n`{implementation_artifacts}\u002F{workflow.case_file_subdir}\u002F{workflow.case_file_filename}` with `{slug}` substituted (slug\nand collision rules in Overview). Create the file from `{workflow.case_file_template}` and fill Hand-off Brief\n(rough), Case Info, Problem Statement, initial Evidence Inventory.\n\n**Evidence-light branch.** When no Confirmed evidence is reachable: mark the case evidence-light in the Hand-off\nBrief; populate the Investigation Backlog with prioritized data-collection items; record \"to make progress, I need one\nof: …\"; pause for the user to provide evidence or authorize Outcome 2 to scan more broadly.\n\nOtherwise present scope, stronghold, file path, proposed approach. Pause for user with the recap above; wait for direction.\n\n### Outcome 2: Evidence perimeter is mapped\n\nSurvey the scene: inventory available evidence in parallel across these independent categories: diagnostic archives;\nissue tracker; version control; test results; static analysis; source code. For any category exceeding ~10K tokens,\ndelegate to a subagent that returns a JSON manifest (paths, sizes, time windows, key fragments cited as `path:line`).\n\nClassify each Available, Partial, or Missing — Missing is itself a finding. Update Evidence Inventory and Investigation\nBacklog. Pause for user with the recap above; wait for direction.\n\n### Outcome 3: Cause is reasoned about with discipline\n\n- **Trace causality.** Symptom-driven: trace backward from the symptom to producing conditions and the state that\n  emerged. Exploration: trace backward from outputs (returns, side effects, messages sent) to producing conditions.\n  Same technique, different anchor.\n- **Reconstruct the timeline** by cross-referencing logs, system events, version control, user observations.\n- **Form and test hypotheses.** State, identify confirming\u002Frefuting evidence, search, grade\n  (Confirmed \u002F Refuted \u002F Open). Update Status. Never delete.\n- **Refutation pass.** Each time a hypothesis transitions toward Confirmed, actively look for refuting evidence first.\n  Record the attempt in Resolution.\n- **Verify the user's premise.** If evidence contradicts, say so explicitly.\n- **Add discovered paths to the backlog.** Stay focused on the current thread.\n\nUpdate Confirmed Findings, Deduced Conclusions, Hypothesized Paths, Backlog, Timeline. Highlight contradictions to the\noriginal premise. Pause for user with the recap above; wait for direction.\n\n### Outcome 4: Source has been traced where it matters\n\nIssue these first-pass scans as parallel tool calls in one message: grep for exact error strings; glob the affected\ndirectory for parallel implementations; `git log` for recent changes.\n\nThen sequentially: read the surrounding code; follow the caller chain; watch for language and process boundary\ncrossings (compiled→scripts, IPC, host→device, configuration flow).\n\nLean by case type:\n\n- **Exploration:** I\u002FO mapping (triggers, outputs, dependencies); frequent-terms scan; control-flow filtering\n  (branches, loops, error handling, state-machine transitions).\n- **Symptom-driven:** depth assessment — is the root cause reachable from local context, or is a broader area model\n  required? Surface escalations; never silently expand scope. Trivial-fix assessment — off-by-one, missing null check,\n  swapped argument → one-line code suggestion or draft diff in the report; non-trivial → stop at the root cause area.\n\nInvestigation stops at the diagnosis; implementation is out of scope. Update Source Code Trace (Error origin, Trigger,\nCondition, Related files; area model when broader). Pause for user with the recap above; wait for direction.\n\n### Outcome 5: Report is finalized and the hand-off is clean\n\nUpdate `{case_file}`:\n\n- **Hand-off Brief** rewritten to final form (3 sentences, 15-second read).\n- **Final Conclusion** with confidence: **High** (Confirmed root cause, deterministic repro), **Medium** (Deduced;\n  minor uncertainty), **Low** (Hypothesized; clear data gap).\n- **Fix direction** when applicable (categorize by mechanism if multiple combine).\n- **Diagnostic steps** if uncertainty remains.\n- **Reproduction Plan** when applicable, or a verification plan for exploration cases.\n- **Status:** Active \u002F Concluded \u002F Blocked on evidence.\n\nPresent the conclusion, then a concrete next-steps menu: trivial fix → `aac-quick-dev`; scope\u002Fplan adjustment →\n`aac-correct-course`; tracked story → `aac-create-story`; fresh review → `aac-code-review`. Recommend the\nhighest-value action. Mitigations and workarounds are generated only on explicit request — investigation stops at the\ndiagnosis. Execute `{workflow.on_complete}` if non-empty. Pause for user with the recap above; wait for direction.\n\n## Follow-up Iterations\n\nContinue work by appending to `{case_file}` under a new `## Follow-up: {YYYY-MM-DD}` block (`#2`, `#3` on same-day\nreentry). The investigation is complete when:\n\n- Root cause is Confirmed.\n- Root cause is Hypothesized with a clear data gap.\n- The mental model is sufficient for the user's stated goal (exploration cases).\n- The backlog contains only items requiring unavailable evidence.\n- The user explicitly concludes.\n","# Investigate\n\n## Overview\n\nReconstruct what's happening, or what an unfamiliar area does, from the available evidence. Produce a structured case\nfile another engineer can pick up cold. Calibrate continuously between defect-chasing (symptom-driven) and\narea-exploration (no symptom); the same discipline applies on both ends.\n\n**Args:** A ticket ID, log file path, diagnostic archive, error message, code area name, problem description, or a path\nto an existing case file. The last form resumes a prior investigation; everything else opens a new case.\n\n**Output:** `{implementation_artifacts}\u002F{workflow.case_file_subdir}\u002F{workflow.case_file_filename}`. Reference inputs\nare recorded; raw content is not read into the parent context until an outcome calls for it.\n\n`{slug}` is the ticket ID when one is provided, otherwise a short descriptive name agreed with the user, sanitized to\nlowercase alphanumeric with hyphens. On collision with an existing case file at the resolved path, ask whether to\nrename to `slug-YYYY-MM-DD.md` or resume the existing file (resuming routes to Outcome 0).\n\nAfter every outcome, present what was learned and pause for the user before continuing.\n\n## Principles\n\n- **Evidence grading.**\n  - **Confirmed.** Directly observed; cite `path:line`, log timestamp, or commit hash.\n  - **Deduced.** Logically follows from Confirmed evidence; show the chain.\n  - **Hypothesized.** Plausible but unconfirmed; state what would confirm or refute it.\n- **Stronghold first.** Anchor in one Confirmed piece of evidence and expand outward. Never start from a theory and\n  hunt for support. When evidence is sparse, switch to evidence-light mode (Outcome 1 branch).\n- **Challenge the premise.** The user's description is a hypothesis, not a fact. Verify independently; if evidence\n  contradicts, say so.\n- **Follow the evidence, not the narrative.** When evidence contradicts the working theory, update the theory — never\n  the other way around. Resist confirmation bias even when the user is convinced.\n- **Hypotheses are never deleted.** Update Status (Open \u002F Confirmed \u002F Refuted) and add a Resolution. Wrong turns are\n  part of the deliverable.\n- **Missing evidence is itself a finding.** Document the gap, what it would resolve, and how to obtain it.\n- **Write it down early.** Initialize the case file as soon as the slug is agreed; it is the persistent state across\n  interruptions.\n- **Path:line citations** use CWD-relative format, no leading `\u002F`, so they're clickable in IDE-embedded terminals.\n- **Delegation discipline.** When a step requires reading 5+ files or any file >10K tokens, delegate to a subagent\n  that returns structured JSON only. Cite `path:line` from the result; don't re-read in the parent.\n- **Issue independent operations in parallel** (multi-grep, multi-read, parallel inventories) — one message, multiple\n  tool calls.\n- **Communication.** Evidence-first language (\"the evidence shows\", \"unconfirmed, requires X to verify\"). No hedging,\n  no narrative.\n\n## On Activation\n\n### Step 1: Resolve the workflow block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\nIf the script fails, stop and surface the error.\n\n### Step 2: Execute prepend steps\n\nRun each entry in `{workflow.activation_steps_prepend}` in order.\n\n### Step 3: Load persistent facts\n\nTreat each entry in `{workflow.persistent_facts}` as foundational context. `file:` prefixes are paths or globs under\n`{project-root}` (load contents); other entries are facts verbatim.\n\n### Step 4: Load config\n\nLoad `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve `{user_name}`, `{communication_language}`,\n`{document_output_language}`, `{implementation_artifacts}`, `{project_knowledge}`. If `{implementation_artifacts}` is\nunresolved, fall back to `.\u002Finvestigations\u002F` and surface the fallback before initializing.\n\n### Step 5: Greet\n\nGreet `{user_name}` in `{communication_language}`.\n\n### Step 6: Execute append steps\n\nRun each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.\n\n### Step 7: Acknowledge and route\n\nAcknowledge the input as a reference (record paths and IDs; don't read raw content). Path to an existing case file →\nOutcome 0. Otherwise → Outcome 1.\n\n## Procedure\n\n### Outcome 0: Existing case is loaded and surfaced\n\nRead the case file. Surface, in order: open hypotheses (Status = Open) with their confirm\u002Frefute criteria; open\nbacklog (Status ≠ Done); missing-evidence rows; last Conclusion with confidence. Ask which thread to pull. New\nevidence opens a new `## Follow-up: {YYYY-MM-DD}` block (append `#2`, `#3` on same-day reentry). Pause for user with the recap above; wait for direction.\n\n### Outcome 1: Scope and stronghold are established\n\nAcknowledge each input shape — record location, scope, time window only; bulk reads happen in Outcome 2.\n\n- **Issue tracker ticket.** Fetch full details via available MCP tools.\n- **Diagnostic archive.** Record path, file count, time window.\n- **Log file or stack trace.** Record path and time window; only the stack frame already in the user's message is in\n  scope here.\n- **Free-text description.** Capture verbatim; treat as hypothesis.\n- **Code area name** (no symptom). Record entry point.\n- **Recent commit area.** Record commit range.\n\nIf the user arrived with a hypothesis, register it as Hypothesis #1. Find the stronghold *independently*; the user's\nhypothesis is one of the things the stronghold validates or refutes.\n\nFind a stronghold: a Confirmed piece of evidence (error message, function name, HTTP route, config parameter, test\ncase). Anchor here.\n\n**Initialize `{case_file}` before branching.** The path is\n`{implementation_artifacts}\u002F{workflow.case_file_subdir}\u002F{workflow.case_file_filename}` with `{slug}` substituted (slug\nand collision rules in Overview). Create the file from `{workflow.case_file_template}` and fill Hand-off Brief\n(rough), Case Info, Problem Statement, initial Evidence Inventory.\n\n**Evidence-light branch.** When no Confirmed evidence is reachable: mark the case evidence-light in the Hand-off\nBrief; populate the Investigation Backlog with prioritized data-collection items; record \"to make progress, I need one\nof: …\"; pause for the user to provide evidence or authorize Outcome 2 to scan more broadly.\n\nOtherwise present scope, stronghold, file path, proposed approach. Pause for user with the recap above; wait for direction.\n\n### Outcome 2: Evidence perimeter is mapped\n\nSurvey the scene: inventory available evidence in parallel across these independent categories: diagnostic archives;\nissue tracker; version control; test results; static analysis; source code. For any category exceeding ~10K tokens,\ndelegate to a subagent that returns a JSON manifest (paths, sizes, time windows, key fragments cited as `path:line`).\n\nClassify each Available, Partial, or Missing — Missing is itself a finding. Update Evidence Inventory and Investigation\nBacklog. Pause for user with the recap above; wait for direction.\n\n### Outcome 3: Cause is reasoned about with discipline\n\n- **Trace causality.** Symptom-driven: trace backward from the symptom to producing conditions and the state that\n  emerged. Exploration: trace backward from outputs (returns, side effects, messages sent) to producing conditions.\n  Same technique, different anchor.\n- **Reconstruct the timeline** by cross-referencing logs, system events, version control, user observations.\n- **Form and test hypotheses.** State, identify confirming\u002Frefuting evidence, search, grade\n  (Confirmed \u002F Refuted \u002F Open). Update Status. Never delete.\n- **Refutation pass.** Each time a hypothesis transitions toward Confirmed, actively look for refuting evidence first.\n  Record the attempt in Resolution.\n- **Verify the user's premise.** If evidence contradicts, say so explicitly.\n- **Add discovered paths to the backlog.** Stay focused on the current thread.\n\nUpdate Confirmed Findings, Deduced Conclusions, Hypothesized Paths, Backlog, Timeline. Highlight contradictions to the\noriginal premise. Pause for user with the recap above; wait for direction.\n\n### Outcome 4: Source has been traced where it matters\n\nIssue these first-pass scans as parallel tool calls in one message: grep for exact error strings; glob the affected\ndirectory for parallel implementations; `git log` for recent changes.\n\nThen sequentially: read the surrounding code; follow the caller chain; watch for language and process boundary\ncrossings (compiled→scripts, IPC, host→device, configuration flow).\n\nLean by case type:\n\n- **Exploration:** I\u002FO mapping (triggers, outputs, dependencies); frequent-terms scan; control-flow filtering\n  (branches, loops, error handling, state-machine transitions).\n- **Symptom-driven:** depth assessment — is the root cause reachable from local context, or is a broader area model\n  required? Surface escalations; never silently expand scope. Trivial-fix assessment — off-by-one, missing null check,\n  swapped argument → one-line code suggestion or draft diff in the report; non-trivial → stop at the root cause area.\n\nInvestigation stops at the diagnosis; implementation is out of scope. Update Source Code Trace (Error origin, Trigger,\nCondition, Related files; area model when broader). Pause for user with the recap above; wait for direction.\n\n### Outcome 5: Report is finalized and the hand-off is clean\n\nUpdate `{case_file}`:\n\n- **Hand-off Brief** rewritten to final form (3 sentences, 15-second read).\n- **Final Conclusion** with confidence: **High** (Confirmed root cause, deterministic repro), **Medium** (Deduced;\n  minor uncertainty), **Low** (Hypothesized; clear data gap).\n- **Fix direction** when applicable (categorize by mechanism if multiple combine).\n- **Diagnostic steps** if uncertainty remains.\n- **Reproduction Plan** when applicable, or a verification plan for exploration cases.\n- **Status:** Active \u002F Concluded \u002F Blocked on evidence.\n\nPresent the conclusion, then a concrete next-steps menu: trivial fix → `aac-quick-dev`; scope\u002Fplan adjustment →\n`aac-correct-course`; tracked story → `aac-create-story`; fresh review → `aac-code-review`. Recommend the\nhighest-value action. Mitigations and workarounds are generated only on explicit request — investigation stops at the\ndiagnosis. Execute `{workflow.on_complete}` if non-empty. Pause for user with the recap above; wait for direction.\n\n## Follow-up Iterations\n\nContinue work by appending to `{case_file}` under a new `## Follow-up: {YYYY-MM-DD}` block (`#2`, `#3` on same-day\nreentry). The investigation is complete when:\n\n- Root cause is Confirmed.\n- Root cause is Hypothesized with a clear data gap.\n- The mental model is sufficient for the user's stated goal (exploration cases).\n- The backlog contains only items requiring unavailable evidence.\n- The user explicitly concludes.\n",{"name":5,"description":7},"main","473351382920a74eb8f353f979a06f6f05bb5f59","resources\u002F_aac\u002Fskills\u002Faac-investigate",0,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt","https:\u002F\u002Fgithub.com\u002Fmsayedshokry","2026-08-29 02:00:07",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-investigate",{"tool":50,"command":51},"bunx","bunx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-investigate",{"tool":53,"command":54},"pnpm","pnpm dlx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-investigate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-investigate\u002FSKILL.md",true,[58,64],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"customize.toml","OTHER","其他",2526,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-investigate\u002Fcustomize.toml",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcase-file-template.md","REFERENCE","参考文档",4134,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-investigate\u002Freferences\u002Fcase-file-template.md",[71,99,117,130,153,168],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":87,"publishedAt":32},"01M6DNRTHE3M1XG3KDJTEF6BG6","bmad-teach-me-testing","Teach testing progressively through structured sessions. Use when user says \"lets learn testing\" or \"I want to study test practices\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Fbmad-teach-me-testing\u002FSKILL.md",[77,82],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[88,89,90,91,92,93,94,95,96,25,26,97,98],"bmad","me","bmad teach me testing","teach me","teach","testing","test","sessions","learn","study","structured",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":32},"01M6DNRG27V77JEGMPMJVRY0Q5","aac-testarch-trace","Generate traceability matrix and quality gate decision. Use when the user says \"lets create traceability matrix\" or \"I want to analyze test coverage\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-trace\u002FSKILL.md",[105],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[107,24,94,108,109,110,111,112,113,25,114,26,115,116],"aac testarch trace","quality gate","create","generate","analyze","quality","decision","coverage","test coverage","gate",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":32},"01M6DNR70G1S0DGDSHRWT1S1DD","aac-testarch-test-review","Review test quality using best practices validation. Use when user says \"lets review tests\" or \"I want to evaluate test quality\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-review\u002FSKILL.md",[123],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[125,126,94,127,128,112,25,26,129],"review","aac testarch test review","best practices","validation","tests",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":143,"publishedAt":32},"01M6DNQXV8F40EE78ZMWGWRPJM","aac-testarch-test-design","Create system-level or epic-level test plans. Use when the user says \"lets design test plan\" or \"I want to create test strategy\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-design\u002FSKILL.md",[136,137,140],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":138,"categoryName":139,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":141,"categoryName":142,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000032","设计师",[144,145,94,146,25,109,147,148,149,150,26,151,152],"aac testarch test design","test design","design","test plan","plan","system","strategy","test strategy","plans",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":32},"01M6DNQNG0T7Q5DKV3C03RY35D","aac-testarch-nfr","Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says \"audit NFR evidence\", \"audit NFRs\", or \"evaluate non-functional requirements\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-nfr\u002FSKILL.md",[],[160,161,27,162,163,164,25,165,166,26,167],"aac testarch nfr","reliability","implementation","scalability","requirements","audit","performance","security",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":32},"01M6DNQDPTGB49D8AAJV4GN2H8","aac-testarch-framework","Initialize test framework with Playwright or Cypress. Use when the user says \"lets setup test framework\" or \"I want to initialize testing framework\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-framework\u002FSKILL.md",[174],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[176,177,178,25,26,179,180,181,94,182,93,183],"aac testarch framework","framework","initialize","testing framework","setup","test framework","playwright","cypress"]