[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DN8DJ5Q6CCZFX388Q7MHSW":3,"skill-same:01M6DN8DJ5Q6CCZFX388Q7MHSW":57},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6DN8DJ5Q6CCZFX388Q7MHSW","aac-architecture-spine",null,"Lean intent-based architecture. Produces an ARCHITECTURE-SPINE.md as the source of truth, with SPEC.md derived. Use when the user wants a fast architecture pass and the multi-step aac-create-architecture flow is too heavy. Menu code AS.","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-architecture-spine\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"architecture","aac architecture spine","spec","create","code","fast","flow","user","lean","use","intent","as","2026-11-10 10:12:30",false,"---\nname: aac-architecture-spine\ndescription: 'Lean intent-based architecture. Produces an ARCHITECTURE-SPINE.md as the source of truth, with SPEC.md derived. Use when the user wants a fast architecture pass and the multi-step aac-create-architecture flow is too heavy. Menu code AS.'\n---\n\n# Architecture Spine\n\nA lean, intent-based architecture flow. Where `aac-create-architecture` is the multi-step, 8-pass, validation-rich path, the spine is a fast route: one prompt, one spine document, one decision.\n\nThe spine is the **source of truth**. `SPEC.md` (when needed) is **derived** from the spine, not authored alongside it. This inverts the usual order and is what makes the spine lean.\n\n## When to Use\n\n- The user says \"I need a quick architecture\" \u002F \"spine\" \u002F \"lean architecture\" \u002F \"intent-based\" \u002F \"AS\"\n- The user has a clear feature slice and just wants the structural decisions captured\n- The user is iterating on an existing spine and wants to update a section\n- The user is migrating from a doc-heavy spec to a leaner model\n\nDo NOT use for:\n\n- Greenfield exploration where the architecture IS the discovery — use `aac-create-architecture`\n- Brownfield reverse-engineering — use `aac-document-project`\n- Test planning — use `aac-tea-test-design`\n\n## The Five Entry Shapes (Intent Routing)\n\nThe spine's power is that it does not impose a single starting point. The user declares their intent; the spine routes accordingly.\n\n| Intent | Entry shape | Spine behaviour |\n|---|---|---|\n| `idea` | A half-formed idea, one paragraph | Generate a full spine from scratch. Heavy lifting on Tech Stack and Data Model. |\n| `doc` | A large doc (PRD, RFC, design doc) | Extract the spine shape from the doc; flag the doc's unstated assumptions. |\n| `codebase` | An existing codebase | Reverse-engineer the spine. Output the spine AND a `drift.md` listing where the code contradicts the spine. |\n| `feature` | A feature slice (story or epic) | Produce a feature-scoped spine — one or two altitudes, not all. |\n| `existing` | An existing spine | Update mode. Apply the user's diff. Preserve all sections the diff does not touch. |\n\nRoutes are detected from the user's first message. The spine asks for clarification only if the intent is genuinely ambiguous.\n\n## On Activation\n\n1. **Parse arguments** — check for `--intent idea|doc|codebase|feature|existing`, `--headless`.\n2. **Load config** from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml`:\n   - `user_name`, `communication_language`, `document_output_language`\n   - `planning_artifacts` (output location)\n3. **Detect the entry shape** from the user's first message. If ambiguous, ask.\n4. **Route to the matching entry shape** below.\n\n### Route: `idea`\n\n- Ask 3-5 questions to nail down: user, problem, why-now, rough shape.\n- Generate the spine from the answers.\n- Apply the breadth-coverage rubric (every altitude-owned dimension decided\u002Fdeferred\u002Fopen).\n\n### Route: `doc`\n\n- Ask the user for the doc path. Load the full doc.\n- Extract the structural decisions: tech stack, data model, API surface, integration points.\n- Surface unstated assumptions — the doc's silence on a dimension is data, not absence.\n- Generate the spine. Note in the spine header which doc was the source.\n\n### Route: `codebase`\n\n- Ask the user for the codebase root path.\n- Reverse-engineer: scan for tech stack markers (package.json, go.mod, pyproject.toml, etc.), route patterns, data model markers.\n- Generate the spine from observed reality.\n- Produce `drift.md` listing places where the code contradicts the spine (or where the spine contradicts the code).\n\n### Route: `feature`\n\n- Ask the user for the feature slice (story ID, epic ID, or free-form description).\n- Produce a feature-scoped spine — only the altitudes affected by this slice.\n- Reference the existing spine (if any) for the altitudes it does not change.\n\n### Route: `existing`\n\n- Ask the user for the existing spine path and the desired change.\n- Apply the change. Preserve all untouched sections verbatim.\n- Run the breadth-coverage rubric on the updated spine.\n\n## The Spine Document\n\n`ARCHITECTURE-SPINE.md` is the source of truth. It is intentionally short. The shape:\n\n```markdown\n# Architecture Spine\n\n**Project:** {project_name}\n**Owner:** {user_name}\n**Last updated:** {date}\n**Source intent:** {idea|doc|codebase|feature|existing}\n\n## Problem\n[1 paragraph. The user. The pain. The why-now.]\n\n## Altitudes\n[Each altitude is one decision. Each is decided|deferred|open.]\n\n### A1. Tech stack\n{decided|deferred|open} — {decision or note}\n\n### A2. Data model\n{decided|deferred|open} — {decision or note}\n\n### A3. API surface\n{decided|deferred|open} — {decision or note}\n\n### A4. Integration points\n{decided|deferred|open} — {decision or note}\n\n### A5. Security posture\n{decided|deferred|open} — {decision or note}\n\n### A6. Observability\n{decided|deferred|open} — {decision or note}\n\n### A7. Deployment topology\n{decided|deferred|open} — {decision or note}\n\n## Rules\n[Each rule is one paragraph. Naming, structure, error handling, communication patterns.]\n\n## Out of scope\n[What this spine explicitly does NOT decide. Saves future debates.]\n\n## Breadth coverage\n[Rubric: every altitude marked. Open items flagged. Deferred items carry a target.]\n\n## Links\n- SPEC: [derived from this spine, when generated]\n- Source doc: [if route = doc]\n- Drift: [drift.md, if route = codebase]\n```\n\nThe spine is a thinking tool, not a contract. SPEC.md is generated **from** the spine when the team needs the full, larger doc.\n\n## SPEC.md Derivation\n\nWhen the user (or `aac-spec`) needs a SPEC, generate it from the spine:\n\n- Tech stack → expands into A1 in SPEC (versions, justification, alternatives rejected)\n- Data model → expands into schema section in SPEC\n- API surface → expands into endpoint tables in SPEC\n- Rules → expand into named pattern sections in SPEC\n- Out of scope → preserved verbatim in SPEC\n\nThe SPEC is generated, not authored. If the user edits SPEC directly, the spine should be the next edit — the spine is the source of truth.\n\n## Headless Mode\n\n`--headless` runs the spine in non-interactive mode:\n\n1. Read the intent from `{project-root}\u002Fspine-input.md` (must declare intent + entry shape).\n2. Run the matching route end-to-end.\n3. Write the spine to `{project-root}\u002FARCHITECTURE-SPINE.md`.\n4. If `--derive-spec` is also set, generate SPEC.md alongside.\n\nHeadless is useful for CI-driven spine generation, overnight batch processing, or for users who want a first-draft spine to react to.\n\n## Success Metrics\n\n- Spine is short (target ≤ 200 lines; the spine that grows past 200 lines has slipped back into SPEC territory)\n- Every altitude is marked decided\u002Fdeferred\u002Fopen (no unmarked altitudes)\n- Open items are not buried; they appear in the breadth-coverage section\n- Out of scope is honest (lists what the spine does NOT cover, not just what it does)\n- SPEC.md derivation is automatic when requested, not hand-authored\n\n## Failure Modes\n\n- Spine growing into a SPEC (use `aac-create-architecture` or `aac-spec` for that)\n- Entry shape not detected (ask, do not guess)\n- Drift.md missing on the codebase route (the spine alone is silent on what reality looks like)\n- Open items hidden in altitude bodies (they belong in the breadth-coverage section)\n- SPEC.md edited without updating the spine (the spine is the source of truth; SPEC is downstream)\n","# Architecture Spine\n\nA lean, intent-based architecture flow. Where `aac-create-architecture` is the multi-step, 8-pass, validation-rich path, the spine is a fast route: one prompt, one spine document, one decision.\n\nThe spine is the **source of truth**. `SPEC.md` (when needed) is **derived** from the spine, not authored alongside it. This inverts the usual order and is what makes the spine lean.\n\n## When to Use\n\n- The user says \"I need a quick architecture\" \u002F \"spine\" \u002F \"lean architecture\" \u002F \"intent-based\" \u002F \"AS\"\n- The user has a clear feature slice and just wants the structural decisions captured\n- The user is iterating on an existing spine and wants to update a section\n- The user is migrating from a doc-heavy spec to a leaner model\n\nDo NOT use for:\n\n- Greenfield exploration where the architecture IS the discovery — use `aac-create-architecture`\n- Brownfield reverse-engineering — use `aac-document-project`\n- Test planning — use `aac-tea-test-design`\n\n## The Five Entry Shapes (Intent Routing)\n\nThe spine's power is that it does not impose a single starting point. The user declares their intent; the spine routes accordingly.\n\n| Intent | Entry shape | Spine behaviour |\n|---|---|---|\n| `idea` | A half-formed idea, one paragraph | Generate a full spine from scratch. Heavy lifting on Tech Stack and Data Model. |\n| `doc` | A large doc (PRD, RFC, design doc) | Extract the spine shape from the doc; flag the doc's unstated assumptions. |\n| `codebase` | An existing codebase | Reverse-engineer the spine. Output the spine AND a `drift.md` listing where the code contradicts the spine. |\n| `feature` | A feature slice (story or epic) | Produce a feature-scoped spine — one or two altitudes, not all. |\n| `existing` | An existing spine | Update mode. Apply the user's diff. Preserve all sections the diff does not touch. |\n\nRoutes are detected from the user's first message. The spine asks for clarification only if the intent is genuinely ambiguous.\n\n## On Activation\n\n1. **Parse arguments** — check for `--intent idea|doc|codebase|feature|existing`, `--headless`.\n2. **Load config** from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml`:\n   - `user_name`, `communication_language`, `document_output_language`\n   - `planning_artifacts` (output location)\n3. **Detect the entry shape** from the user's first message. If ambiguous, ask.\n4. **Route to the matching entry shape** below.\n\n### Route: `idea`\n\n- Ask 3-5 questions to nail down: user, problem, why-now, rough shape.\n- Generate the spine from the answers.\n- Apply the breadth-coverage rubric (every altitude-owned dimension decided\u002Fdeferred\u002Fopen).\n\n### Route: `doc`\n\n- Ask the user for the doc path. Load the full doc.\n- Extract the structural decisions: tech stack, data model, API surface, integration points.\n- Surface unstated assumptions — the doc's silence on a dimension is data, not absence.\n- Generate the spine. Note in the spine header which doc was the source.\n\n### Route: `codebase`\n\n- Ask the user for the codebase root path.\n- Reverse-engineer: scan for tech stack markers (package.json, go.mod, pyproject.toml, etc.), route patterns, data model markers.\n- Generate the spine from observed reality.\n- Produce `drift.md` listing places where the code contradicts the spine (or where the spine contradicts the code).\n\n### Route: `feature`\n\n- Ask the user for the feature slice (story ID, epic ID, or free-form description).\n- Produce a feature-scoped spine — only the altitudes affected by this slice.\n- Reference the existing spine (if any) for the altitudes it does not change.\n\n### Route: `existing`\n\n- Ask the user for the existing spine path and the desired change.\n- Apply the change. Preserve all untouched sections verbatim.\n- Run the breadth-coverage rubric on the updated spine.\n\n## The Spine Document\n\n`ARCHITECTURE-SPINE.md` is the source of truth. It is intentionally short. The shape:\n\n```markdown\n# Architecture Spine\n\n**Project:** {project_name}\n**Owner:** {user_name}\n**Last updated:** {date}\n**Source intent:** {idea|doc|codebase|feature|existing}\n\n## Problem\n[1 paragraph. The user. The pain. The why-now.]\n\n## Altitudes\n[Each altitude is one decision. Each is decided|deferred|open.]\n\n### A1. Tech stack\n{decided|deferred|open} — {decision or note}\n\n### A2. Data model\n{decided|deferred|open} — {decision or note}\n\n### A3. API surface\n{decided|deferred|open} — {decision or note}\n\n### A4. Integration points\n{decided|deferred|open} — {decision or note}\n\n### A5. Security posture\n{decided|deferred|open} — {decision or note}\n\n### A6. Observability\n{decided|deferred|open} — {decision or note}\n\n### A7. Deployment topology\n{decided|deferred|open} — {decision or note}\n\n## Rules\n[Each rule is one paragraph. Naming, structure, error handling, communication patterns.]\n\n## Out of scope\n[What this spine explicitly does NOT decide. Saves future debates.]\n\n## Breadth coverage\n[Rubric: every altitude marked. Open items flagged. Deferred items carry a target.]\n\n## Links\n- SPEC: [derived from this spine, when generated]\n- Source doc: [if route = doc]\n- Drift: [drift.md, if route = codebase]\n```\n\nThe spine is a thinking tool, not a contract. SPEC.md is generated **from** the spine when the team needs the full, larger doc.\n\n## SPEC.md Derivation\n\nWhen the user (or `aac-spec`) needs a SPEC, generate it from the spine:\n\n- Tech stack → expands into A1 in SPEC (versions, justification, alternatives rejected)\n- Data model → expands into schema section in SPEC\n- API surface → expands into endpoint tables in SPEC\n- Rules → expand into named pattern sections in SPEC\n- Out of scope → preserved verbatim in SPEC\n\nThe SPEC is generated, not authored. If the user edits SPEC directly, the spine should be the next edit — the spine is the source of truth.\n\n## Headless Mode\n\n`--headless` runs the spine in non-interactive mode:\n\n1. Read the intent from `{project-root}\u002Fspine-input.md` (must declare intent + entry shape).\n2. Run the matching route end-to-end.\n3. Write the spine to `{project-root}\u002FARCHITECTURE-SPINE.md`.\n4. If `--derive-spec` is also set, generate SPEC.md alongside.\n\nHeadless is useful for CI-driven spine generation, overnight batch processing, or for users who want a first-draft spine to react to.\n\n## Success Metrics\n\n- Spine is short (target ≤ 200 lines; the spine that grows past 200 lines has slipped back into SPEC territory)\n- Every altitude is marked decided\u002Fdeferred\u002Fopen (no unmarked altitudes)\n- Open items are not buried; they appear in the breadth-coverage section\n- Out of scope is honest (lists what the spine does NOT cover, not just what it does)\n- SPEC.md derivation is automatic when requested, not hand-authored\n\n## Failure Modes\n\n- Spine growing into a SPEC (use `aac-create-architecture` or `aac-spec` for that)\n- Entry shape not detected (ask, do not guess)\n- Drift.md missing on the codebase route (the spine alone is silent on what reality looks like)\n- Open items hidden in altitude bodies (they belong in the breadth-coverage section)\n- SPEC.md edited without updating the spine (the spine is the source of truth; SPEC is downstream)\n",{"name":5,"description":7},"main","473351382920a74eb8f353f979a06f6f05bb5f59","resources\u002F_aac\u002Fskills\u002Faac-architecture-spine",0,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt","https:\u002F\u002Fgithub.com\u002Fmsayedshokry","2026-08-29 02:00:07",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-architecture-spine",{"tool":49,"command":50},"bunx","bunx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-architecture-spine",{"tool":52,"command":53},"pnpm","pnpm dlx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-architecture-spine","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-architecture-spine\u002FSKILL.md",true,[],[58,86,104,117,140,156],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":74,"publishedAt":31},"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",[64,69],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[75,76,77,78,79,80,81,82,83,26,28,84,85],"bmad","me","bmad teach me testing","teach me","teach","testing","test","sessions","learn","study","structured",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":93,"publishedAt":31},"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",[92],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[94,95,81,96,22,97,98,99,100,26,101,28,102,103],"aac testarch trace","trace","quality gate","generate","analyze","quality","decision","coverage","test coverage","gate",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":31},"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",[110],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[112,113,81,114,115,99,26,28,116],"review","aac testarch test review","best practices","validation","tests",{"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":130,"publishedAt":31},"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",[123,124,127],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},{"categoryNo":125,"categoryName":126,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":128,"categoryName":129,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000032","设计师",[131,132,81,133,26,22,134,135,136,137,28,138,139],"aac testarch test design","test design","design","test plan","plan","system","strategy","test strategy","plans",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":31},"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",[],[147,148,149,150,151,152,26,153,154,28,155],"aac testarch nfr","reliability","evidence","implementation","scalability","requirements","audit","performance","security",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":31},"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",[162],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[164,165,166,26,28,167,168,169,81,170,80,171],"aac testarch framework","framework","initialize","testing framework","setup","test framework","playwright","cypress"]