[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWNH5A3EN9A2YRPF52KT7C":3,"skill-same:01M7CWNH5A3EN9A2YRPF52KT7C":96},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CWNH5A3EN9A2YRPF52KT7C","plan",null,"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.","haidonglethqb\u002FBAHAU","haidonglethqb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115625430?v=4","01M7CW8M42R8EJ7G0P4XPYEE5D","HAI","01M7CW8M550DFW4TEHPTGEA1S8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan\ndescription: \"Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.\"\nargument-hint: \"[task] OR archive|red-team|validate\"\nlicense: MIT\n---\n\n# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## Default (No Arguments)\n\nIf invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, use `AskUserQuestion` to present available operations:\n\n| Operation | Description |\n|-----------|-------------|\n| `(default)` | Create implementation plan for a task |\n| `archive` | Write journal entry & archive plans |\n| `red-team` | Adversarial plan review |\n| `validate` | Critical questions interview |\n\nPresent as options via `AskUserQuestion` with header \"Planning Operation\", question \"What would you like to do?\".\n\n## Workflow Modes\n\nDefault: `--auto` (analyze task complexity and auto-pick mode).\n\n| Flag | Mode | Research | Red Team | Validation | Cook Flag |\n|------|------|----------|----------|------------|-----------|\n| `--auto` | Auto-detect | Follows mode | Follows mode | Follows mode | Follows mode |\n| `--fast` | Fast | Skip | Skip | Skip | `--auto` |\n| `--hard` | Hard | 2 researchers | Yes | Optional | (none) |\n| `--parallel` | Parallel | 2 researchers | Yes | Optional | `--parallel` |\n| `--two` | Two approaches | 2+ researchers | After selection | After selection | (none) |\n\nAdd `--no-tasks` to skip task hydration in any mode.\n\nLoad: `references\u002Fworkflow-modes.md` for auto-detection logic, per-mode workflows, context reminders.\n\n## When to Use\n\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n\n## Core Responsibilities & Rules\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### 1. Research & Analysis\nLoad: `references\u002Fresearch-phase.md`\n**Skip if:** Fast mode or provided with researcher reports\n\n### 2. Codebase Understanding\nLoad: `references\u002Fcodebase-understanding.md`\n**Skip if:** Provided with scout reports\n\n### 3. Solution Design\nLoad: `references\u002Fsolution-design.md`\n\n### 4. Plan Creation & Organization\nLoad: `references\u002Fplan-organization.md`\n\n### 5. Task Breakdown & Output Standards\nLoad: `references\u002Foutput-standards.md`\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n2. **Mode Detection** → Auto-detect or use explicit flag (see `workflow-modes.md`)\n3. **Research Phase** → Spawn researchers (skip in fast mode)\n4. **Codebase Analysis** → Read docs, scout if needed\n5. **Plan Documentation** → Write comprehensive plan via planner subagent\n6. **Red Team Review** → Use `Skill` tool: `plan:red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Use `Skill` tool: `plan:validate {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n8. **Hydrate Tasks** → Create Claude Tasks from phases (default on, `--no-tasks` to skip)\n9. **Context Reminder** → Output cook command with absolute path (MANDATORY)\n\n## Output Requirements\n\n- DO NOT implement code - only create plans\n- Respond with plan file path and summary\n- Ensure self-contained plans with necessary context\n- Include code snippets\u002Fpseudocode when clarifying\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file\n\n## Task Management\n\nPlan files = persistent. Tasks = session-scoped. Hydration bridges the gap.\n\n**Default:** Auto-hydrate tasks after plan files are written. Skip with `--no-tasks`.\n**3-Task Rule:** \u003C3 phases → skip task creation.\n\nLoad: `references\u002Ftask-management.md` for hydration pattern, TaskCreate patterns, cook handoff protocol.\n\n### Hydration Workflow\n1. Write plan.md + phase files (persistent layer)\n2. TaskCreate per phase with `addBlockedBy` chain\n3. TaskCreate for critical\u002Fhigh-risk steps within phases\n4. Metadata: phase, priority, effort, planDir, phaseFile\n5. Cook picks up via TaskList (same session) or re-hydrates (new session)\n\n## Active Plan State\n\nCheck `## Plan Context` injected by hooks:\n- **\"Plan: {path}\"** → Active plan. Ask \"Continue? [Y\u002Fn]\"\n- **\"Suggested: {path}\"** → Branch hint only. Ask if activate or create new.\n- **\"Plan: none\"** → Create new using `Plan dir:` from `## Naming`\n\nAfter creating plan: `node .claude\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n## Subcommands\n\n| Subcommand | Reference | Purpose |\n|------------|-----------|---------|\n| `\u002Fck:plan archive` | `references\u002Farchive-workflow.md` | Archive plans + write journal entries |\n| `\u002Fck:plan red-team` | `references\u002Fred-team-workflow.md` | Adversarial plan review with hostile reviewers |\n| `\u002Fck:plan validate` | `references\u002Fvalidate-workflow.md` | Validate plan with critical questions interview |\n\n## Quality Standards\n\n- Thorough and specific, consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Detailed enough for junior developers\n- Validate against existing codebase patterns\n\n**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.\n","# Planning\n\nCreate detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.\n\n## Default (No Arguments)\n\nIf invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent, use `AskUserQuestion` to present available operations:\n\n| Operation | Description |\n|-----------|-------------|\n| `(default)` | Create implementation plan for a task |\n| `archive` | Write journal entry & archive plans |\n| `red-team` | Adversarial plan review |\n| `validate` | Critical questions interview |\n\nPresent as options via `AskUserQuestion` with header \"Planning Operation\", question \"What would you like to do?\".\n\n## Workflow Modes\n\nDefault: `--auto` (analyze task complexity and auto-pick mode).\n\n| Flag | Mode | Research | Red Team | Validation | Cook Flag |\n|------|------|----------|----------|------------|-----------|\n| `--auto` | Auto-detect | Follows mode | Follows mode | Follows mode | Follows mode |\n| `--fast` | Fast | Skip | Skip | Skip | `--auto` |\n| `--hard` | Hard | 2 researchers | Yes | Optional | (none) |\n| `--parallel` | Parallel | 2 researchers | Yes | Optional | `--parallel` |\n| `--two` | Two approaches | 2+ researchers | After selection | After selection | (none) |\n\nAdd `--no-tasks` to skip task hydration in any mode.\n\nLoad: `references\u002Fworkflow-modes.md` for auto-detection logic, per-mode workflows, context reminders.\n\n## When to Use\n\n- Planning new feature implementations\n- Architecting system designs\n- Evaluating technical approaches\n- Creating implementation roadmaps\n- Breaking down complex requirements\n\n## Core Responsibilities & Rules\n\nAlways honoring **YAGNI**, **KISS**, and **DRY** principles.\n**Be honest, be brutal, straight to the point, and be concise.**\n\n### 1. Research & Analysis\nLoad: `references\u002Fresearch-phase.md`\n**Skip if:** Fast mode or provided with researcher reports\n\n### 2. Codebase Understanding\nLoad: `references\u002Fcodebase-understanding.md`\n**Skip if:** Provided with scout reports\n\n### 3. Solution Design\nLoad: `references\u002Fsolution-design.md`\n\n### 4. Plan Creation & Organization\nLoad: `references\u002Fplan-organization.md`\n\n### 5. Task Breakdown & Output Standards\nLoad: `references\u002Foutput-standards.md`\n\n## Workflow Process\n\n1. **Pre-Creation Check** → Check Plan Context for active\u002Fsuggested\u002Fnone\n2. **Mode Detection** → Auto-detect or use explicit flag (see `workflow-modes.md`)\n3. **Research Phase** → Spawn researchers (skip in fast mode)\n4. **Codebase Analysis** → Read docs, scout if needed\n5. **Plan Documentation** → Write comprehensive plan via planner subagent\n6. **Red Team Review** → Use `Skill` tool: `plan:red-team {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n7. **Post-Plan Validation** → Use `Skill` tool: `plan:validate {plan-path}` (hard\u002Fparallel\u002Ftwo modes)\n8. **Hydrate Tasks** → Create Claude Tasks from phases (default on, `--no-tasks` to skip)\n9. **Context Reminder** → Output cook command with absolute path (MANDATORY)\n\n## Output Requirements\n\n- DO NOT implement code - only create plans\n- Respond with plan file path and summary\n- Ensure self-contained plans with necessary context\n- Include code snippets\u002Fpseudocode when clarifying\n- Fully respect the `.\u002Fdocs\u002Fdevelopment-rules.md` file\n\n## Task Management\n\nPlan files = persistent. Tasks = session-scoped. Hydration bridges the gap.\n\n**Default:** Auto-hydrate tasks after plan files are written. Skip with `--no-tasks`.\n**3-Task Rule:** \u003C3 phases → skip task creation.\n\nLoad: `references\u002Ftask-management.md` for hydration pattern, TaskCreate patterns, cook handoff protocol.\n\n### Hydration Workflow\n1. Write plan.md + phase files (persistent layer)\n2. TaskCreate per phase with `addBlockedBy` chain\n3. TaskCreate for critical\u002Fhigh-risk steps within phases\n4. Metadata: phase, priority, effort, planDir, phaseFile\n5. Cook picks up via TaskList (same session) or re-hydrates (new session)\n\n## Active Plan State\n\nCheck `## Plan Context` injected by hooks:\n- **\"Plan: {path}\"** → Active plan. Ask \"Continue? [Y\u002Fn]\"\n- **\"Suggested: {path}\"** → Branch hint only. Ask if activate or create new.\n- **\"Plan: none\"** → Create new using `Plan dir:` from `## Naming`\n\nAfter creating plan: `node .claude\u002Fscripts\u002Fset-active-plan.cjs {plan-dir}`\nReports: Active plans → plan-specific path. Suggested → default path.\n\n### Important\nDO NOT create plans or reports in USER directory.\nALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.\n\n## Subcommands\n\n| Subcommand | Reference | Purpose |\n|------------|-----------|---------|\n| `\u002Fck:plan archive` | `references\u002Farchive-workflow.md` | Archive plans + write journal entries |\n| `\u002Fck:plan red-team` | `references\u002Fred-team-workflow.md` | Adversarial plan review with hostile reviewers |\n| `\u002Fck:plan validate` | `references\u002Fvalidate-workflow.md` | Validate plan with critical questions interview |\n\n## Quality Standards\n\n- Thorough and specific, consider long-term maintainability\n- Research thoroughly when uncertain\n- Address security and performance concerns\n- Detailed enough for junior developers\n- Validate against existing codebase patterns\n\n**Remember:** Plan quality determines implementation success. Be comprehensive and consider all solution aspects.\n",{"name":5,"license":15,"description":7,"argument-hint":24},"[task] OR archive|red-team|validate","main","82da5963278d597455c869ad91cfc05b2b607e75",".claude\u002Fskills\u002Fplan","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb","Study at University of information technology - Viet Nam National University","2026-11-12 17:30:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add haidonglethqb\u002FBAHAU --skill plan",{"tool":38,"command":39},"bunx","bunx skills add haidonglethqb\u002FBAHAU --skill plan",{"tool":41,"command":42},"pnpm","pnpm dlx skills add haidonglethqb\u002FBAHAU --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Farchive-workflow.md","REFERENCE","参考文档",2336,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Farchive-workflow.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcodebase-understanding.md",1973,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fcodebase-understanding.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Foutput-standards.md",4571,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Foutput-standards.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fplan-organization.md",3705,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fplan-organization.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fred-team-personas.md",2621,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fred-team-personas.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fred-team-workflow.md",2684,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fred-team-workflow.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fresearch-phase.md",1578,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fresearch-phase.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fsolution-design.md",2057,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fsolution-design.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Ftask-management.md",5631,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Ftask-management.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fvalidate-question-framework.md",2361,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fvalidate-question-framework.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fvalidate-workflow.md",2306,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fvalidate-workflow.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflow-modes.md",5737,"https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fplan\u002Freferences\u002Fworkflow-modes.md",[97,105,112,120,127,135],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7CX33YDC6KGJ0E8BXAZPJ5F","ck:web-testing","Web testing with Playwright, Vitest, k6. E2E\u002Funit\u002Fintegration\u002Fload\u002Fsecurity\u002Fvisual\u002Fa11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fweb-testing\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7CX2ZQD1ZYDCPDXV9RT172S","ck:web-frameworks","Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7CX2AAFYCVRJVP668GQGWEG","ck:ui-styling","Style UIs with shadcn\u002Fui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7CX23C6RSSS5YQZTT9C86GC","ck:threejs","Build 3D web apps with Three.js (WebGL\u002FWebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR\u002FXR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7CX1CJVKAQJHM6VSEFMNCHX","ck:skill-creator","Create or update Claude skills optimized for Skillmark benchmarks. Use for new skills, skill scripts, references, benchmark optimization, extending Claude's capabilities.","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M7CX115W0PP7J9CDDZZQGH0M","ck:sequential-thinking","Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.","https:\u002F\u002Fgithub.com\u002Fhaidonglethqb\u002FBAHAU\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[]]