[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T8HD3C1RG368FJDV338MR":3,"skill-same:01M79T8HD3C1RG368FJDV338MR":62},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M79T8HD3C1RG368FJDV338MR","subagent-driven-development",null,"Execute plans via delegate_to_subagent subagents (2-stage review).","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fsubagent-driven-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: subagent-driven-development\ndescription: \"Execute plans via delegate_to_subagent subagents (2-stage review).\"\nversion: 1.2.0\nauthor: Hermes Agent (adapted from obra\u002Fsuperpowers), ported for CrusorAI\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [delegation, subagent, implementation, workflow, parallel]\n    related_skills: [requesting-code-review, test-driven-development]\n---\n\n**Triggers:** subagent, sub-agent, delegate, parallel agents, spawn agents, batch agents, delegate_to_subagent, fan out, startup, platform, ecommerce, e-commerce, amazon, fullstack, multi-tier, complex project\n\n# Subagent-Driven Development\n\n## Overview\n\nExecute an implementation plan by dispatching a fresh Crusor subagent per task with systematic two-stage review.\n\n**Core principle:** fresh subagent per task + two-stage review (spec, then quality) = high quality, fast iteration. Crusor already ships `delegate_to_subagent` (single) and `delegate_to_subagent_batch` (parallel) — this skill is about driving them well.\n\n## When to Use\n\n- You have an implementation plan (Plan mode output or user requirements)\n- Tasks are mostly independent\n- Quality and spec compliance matter\n\n**vs. manual execution:** fresh context per task (no confusion from accumulated state), automated review catches issues early, consistent quality checks. Child runs are isolated (`parentMap`), depth-guarded by `CRUSORAI_SUBAGENT_DEPTH`, and surface as clickable `taskToolCard`s — tell the user they can click through to each child.\n\n## The Process\n\n### 1. Read and Parse the Plan ONCE\n\nExtract ALL tasks with their full text and context upfront. **Do not make subagents read the plan file — paste the full task text into each subagent's context.**\n\n### 2. Per-Task Workflow\n\n#### Step 1 — dispatch the implementer\n\nUse `delegate_to_subagent` with complete, self-sufficient context:\n\n```python\ndelegate_to_subagent(\n    goal=\"Implement Task 1: Create User model with email and password_hash fields\",\n    context=\"\"\"\n    TASK FROM PLAN:\n    - Create: src\u002Fmodels\u002Fuser.py\n    - User class with email (str) and password_hash (str); bcrypt hashing\n\n    FOLLOW TDD (test-driven-development skill):\n    1. Write failing test in tests\u002Fmodels\u002Ftest_user.py\n    2. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v   (verify FAIL)\n    3. Minimal implementation\n    4. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v   (verify PASS)\n    5. Run: pytest tests\u002F -q                      (no regressions)\n\n    PROJECT CONTEXT: Python 3.12, app in src\u002F, pytest from project root.\n    \"\"\",\n)\n```\n\n#### Step 2 — spec-compliance reviewer\n\nAfter the implementer completes, dispatch a fresh subagent that checks ONLY against the original spec:\n\n```text\nCHECK: all spec requirements implemented? file paths\u002Fsignatures match?\nbehavior matches? nothing extra added (no scope creep)?\nOUTPUT: PASS, or a list of specific spec gaps to fix.\n```\n\nIf gaps: fix, then re-run the spec review. Continue only when spec-compliant.\n\n#### Step 3 — code-quality reviewer\n\n```text\nCHECK: project conventions? error handling? clear names? test coverage?\nobvious bugs\u002Fedge cases? security issues?\nOUTPUT: Critical \u002F Important \u002F Minor issues + verdict APPROVED or REQUEST_CHANGES.\n```\n\nIf issues: fix, re-review. Continue only when approved.\n\n#### Step 4 — mark the task complete and move to the next\n\n### 3. Parallelize Independent Tasks\n\nIndependent tasks (different files, no interface coupling) go through `delegate_to_subagent_batch` in ONE call. Dependencies stay serial: never dispatch a task whose inputs another subagent is still producing.\n\n### 4. Final Integration Review\n\nAfter ALL tasks complete, dispatch one final reviewer: do the components work together? inconsistencies between tasks? all tests passing? ready for hand-off?\n\n## Invariants\n\n- Fresh subagent per task and per review — never ask the implementer to review itself.\n- Reviews read files only; fixes go back through an implementer dispatch.\n- Never commit without the user's approval flow (Crusor mutation gates).\n- If a subagent fails twice on the same task, stop and escalate to the user instead of retrying blindly.\n","**Triggers:** subagent, sub-agent, delegate, parallel agents, spawn agents, batch agents, delegate_to_subagent, fan out, startup, platform, ecommerce, e-commerce, amazon, fullstack, multi-tier, complex project\n\n# Subagent-Driven Development\n\n## Overview\n\nExecute an implementation plan by dispatching a fresh Crusor subagent per task with systematic two-stage review.\n\n**Core principle:** fresh subagent per task + two-stage review (spec, then quality) = high quality, fast iteration. Crusor already ships `delegate_to_subagent` (single) and `delegate_to_subagent_batch` (parallel) — this skill is about driving them well.\n\n## When to Use\n\n- You have an implementation plan (Plan mode output or user requirements)\n- Tasks are mostly independent\n- Quality and spec compliance matter\n\n**vs. manual execution:** fresh context per task (no confusion from accumulated state), automated review catches issues early, consistent quality checks. Child runs are isolated (`parentMap`), depth-guarded by `CRUSORAI_SUBAGENT_DEPTH`, and surface as clickable `taskToolCard`s — tell the user they can click through to each child.\n\n## The Process\n\n### 1. Read and Parse the Plan ONCE\n\nExtract ALL tasks with their full text and context upfront. **Do not make subagents read the plan file — paste the full task text into each subagent's context.**\n\n### 2. Per-Task Workflow\n\n#### Step 1 — dispatch the implementer\n\nUse `delegate_to_subagent` with complete, self-sufficient context:\n\n```python\ndelegate_to_subagent(\n    goal=\"Implement Task 1: Create User model with email and password_hash fields\",\n    context=\"\"\"\n    TASK FROM PLAN:\n    - Create: src\u002Fmodels\u002Fuser.py\n    - User class with email (str) and password_hash (str); bcrypt hashing\n\n    FOLLOW TDD (test-driven-development skill):\n    1. Write failing test in tests\u002Fmodels\u002Ftest_user.py\n    2. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v   (verify FAIL)\n    3. Minimal implementation\n    4. Run: pytest tests\u002Fmodels\u002Ftest_user.py -v   (verify PASS)\n    5. Run: pytest tests\u002F -q                      (no regressions)\n\n    PROJECT CONTEXT: Python 3.12, app in src\u002F, pytest from project root.\n    \"\"\",\n)\n```\n\n#### Step 2 — spec-compliance reviewer\n\nAfter the implementer completes, dispatch a fresh subagent that checks ONLY against the original spec:\n\n```text\nCHECK: all spec requirements implemented? file paths\u002Fsignatures match?\nbehavior matches? nothing extra added (no scope creep)?\nOUTPUT: PASS, or a list of specific spec gaps to fix.\n```\n\nIf gaps: fix, then re-run the spec review. Continue only when spec-compliant.\n\n#### Step 3 — code-quality reviewer\n\n```text\nCHECK: project conventions? error handling? clear names? test coverage?\nobvious bugs\u002Fedge cases? security issues?\nOUTPUT: Critical \u002F Important \u002F Minor issues + verdict APPROVED or REQUEST_CHANGES.\n```\n\nIf issues: fix, re-review. Continue only when approved.\n\n#### Step 4 — mark the task complete and move to the next\n\n### 3. Parallelize Independent Tasks\n\nIndependent tasks (different files, no interface coupling) go through `delegate_to_subagent_batch` in ONE call. Dependencies stay serial: never dispatch a task whose inputs another subagent is still producing.\n\n### 4. Final Integration Review\n\nAfter ALL tasks complete, dispatch one final reviewer: do the components work together? inconsistencies between tasks? all tests passing? ready for hand-off?\n\n## Invariants\n\n- Fresh subagent per task and per review — never ask the implementer to review itself.\n- Reviews read files only; fixes go back through an implementer dispatch.\n- Never commit without the user's approval flow (Crusor mutation gates).\n- If a subagent fails twice on the same task, stop and escalate to the user instead of retrying blindly.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":37,"description":7},"Hermes Agent (adapted from obra\u002Fsuperpowers), ported for CrusorAI","1.2.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"delegation","subagent","implementation","workflow","parallel",[35,36],"requesting-code-review","test-driven-development",[38,39,40],"linux","macos","windows","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fsubagent-driven-development","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill subagent-driven-development",{"tool":54,"command":55},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill subagent-driven-development",{"tool":57,"command":58},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill subagent-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fsubagent-driven-development\u002FSKILL.md",true,[],[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]