[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DRT2RVDAWHKF3YQE06GP4M":3,"skill-same:01M6DRT2RVDAWHKF3YQE06GP4M":78},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6DRT2RVDAWHKF3YQE06GP4M","bootstrap-feature",null,"Run the documentation phase of the SDLC pipeline for a feature — PRD, use cases, architecture review, QA test cases, implementation plan, feature branch and scratchpad. Produces no code.","Koroqe\u002Fclaude-code-sdlc","Koroqe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F24411116?v=4","01M6DRMM7GVYYXKEW474YPDVNG","Aleksei Korobeinikov","01M6DRMMBZ82MW04MVQ3Q9M5N5",53,"MIT","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fbootstrap-feature\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"feature","bootstrap feature","bootstrap","Bash","no code","use","edit","write","read","branch","plan","review","qa test","pipeline","qa","code","run","architecture review","documentation","architecture","2026-11-10 10:12:30",false,"---\ndescription: Run the documentation phase of the SDLC pipeline for a feature — PRD, use cases, architecture review, QA test cases, implementation plan, feature branch and scratchpad. Produces no code.\nargument-hint: \"\u003Cfeature description>\"\narguments: [feature]\nallowed-tools: Read, Glob, Grep, Edit, Write, Bash, Agent, TodoWrite\n---\n\n# Command: Bootstrap Feature\n\n## Arguments\n\nThe feature to document is `$feature` (also available as `$ARGUMENTS`). When it is empty, ask the user what to document before Step 1 — do NOT infer a feature from surrounding context.\n\n**Literal-token flag rule:** a documented flag is active ONLY if its literal token appears in `$ARGUMENTS`. Never infer that a flag was passed because the documentation describes it.\n\n## Preflight: Memory Layer Check\n\nRun this FIRST, before Step 1. It takes one Read.\n\n1. Check that `~\u002F.claude\u002Fclaude.md` exists and contains the marker heading `## Autonomous Development Workflow (MANDATORY)`.\n2. If the file is missing, or the marker is absent, print this warning verbatim and **continue anyway**:\n\n   > WARNING: the SDLC memory layer is not installed. `~\u002F.claude\u002Fclaude.md` is missing or does not\n   > contain the pipeline instruction, so the autonomous workflow is not active for unprefixed\n   > requests in this session. Installing the plugin alone is not sufficient — run\n   > `bash install.sh` from the claude-code-sdlc repo to install the memory layer.\n\n3. **Never block on this check.** A missing memory layer degrades autonomy; it does not invalidate this run. Warn once and proceed to Step 1.\n\nKnown limitation: this preflight only fires when this skill is invoked explicitly. An unprefixed natural-language feature request bypasses it entirely, because nothing runs. That gap closes when the SessionStart hook lands (roadmap F2a).\n\n## Agency Documentation Pipeline\n\nEvery feature follows this pipeline before any code is written. Each step is performed by a specialized agent role.\n\n### Step 1: Product Manager — PRD Documentation\nDelegate to `prd-writer` agent:\n- Read `docs\u002FPRD.md` to understand the existing format\n- Add a new section documenting the feature's requirements\n- Include: feature description, user story, functional\u002Fnon-functional requirements, acceptance criteria, affected endpoints, schema changes, UI changes\n\n### Step 2: Business Analyst — Use Cases\nDelegate to `ba-analyst` agent:\n- Read `docs\u002FPRD.md` for the feature requirements just documented\n- Create `docs\u002Fuse-cases\u002F\u003Cfeature-slug>_use_cases.md`\n- Document ALL scenarios: primary flows, alternative flows, error flows, edge cases\n- Include actors, preconditions, postconditions, data requirements\n- This document becomes the blueprint for E2E testing\n\n### Step 3: Software Architect — Architecture Review\nDelegate to `architect` agent:\n- Read PRD and use-case documents\n- Validate the approach against project structure defined in CLAUDE.md\n- Check module boundaries\n- Review any schema changes for data integrity\n- Verify API design follows REST conventions\n- Flag components needing security pre-review during implementation\n\n#### If Architecture Review FAILS:\n1. Read the architect's specific objections\n2. Revise the approach to address each violation\n3. Re-submit to `architect` for review\n4. Retry up to 2 times\n5. If still rejected: document the architectural concern in scratchpad as a blocker and ask the user\n\n### Step 4: QA Lead — Test Case Documentation\nDelegate to `qa-planner` agent:\n- Read `docs\u002FPRD.md` AND `docs\u002Fuse-cases\u002F\u003Cfeature-slug>_use_cases.md`\n- Create `docs\u002Fqa\u002F\u003Cfeature-slug>_test_cases.md`\n- Map every use-case scenario to test cases (UC-1 → TC-1.1, UC-1-E1 → TC-1.2, etc.)\n- Cover: happy path, alternative flows, errors, edge cases, auth boundaries, concurrency\n\n### Step 5: Tech Lead — Implementation Planning\nDelegate to `planner` agent:\n- Read ALL documentation created above: PRD, use cases, architecture review, test cases\n- Read the project's CLAUDE.md for file structure and conventions\n- Break the feature into 5-9 testable implementation slices\n- Each slice references which use-case scenarios it implements (UC-X.Y)\n- Flag slices needing architect or security pre-review\n- Reference actual project files discovered during exploration\n\n#### Step 5a: Plan Critic — Adversarial Plan Review\nAfter the `planner` agent produces the plan and before Step 6 (Git Setup), invoke `plan-critic` against the plan file. This is the first point at which a plan produced entirely by `\u002Fbootstrap-feature` (no interactive plan-mode involved) is critiqued at all.\n\nRun the same critique-and-fix loop `src\u002Fclaude.md`'s plan-mode \"Plan Critic Pass\" section uses:\n1. Invoke `plan-critic` against the plan file (loop 1).\n2. **Fix the plan file for every BLOCKER and every WARNING finding. This fix pass always runs whenever there is at least one BLOCKER or WARNING — it is NOT conditional on a BLOCKER being present.** WARNING is where Scope Reduction Detection lands, and hedging findings must be fixed rather than merely noted.\n2b. **Re-invoke only if a BLOCKER was found** in the loop just completed (loop 2) — the loop repeats on BLOCKERs, the fixing covers WARNINGs too.\n3. Repeat once more if needed (loop 3).\n4. If zero BLOCKER findings remain after any loop, proceed to Step 6 — having already applied the step-2 fixes. Any WARNING deliberately not fixed is recorded with its justification.\n5. If a BLOCKER finding still remains after loop 3, escalate per Rule 4 (`error-recovery.md`): stop, present the remaining BLOCKER findings verbatim, state the decision needed, and present the options. Do NOT proceed to Step 6 with an unresolved BLOCKER.\n\nIf `plan-critic` cannot be resolved (memory-layer-only install with no plugin agents present), warn — naming `plan-critic` explicitly as unresolvable — and proceed to Step 6 without a critique. Never skip the critic pass silently.\n\n### Step 6: Git Setup\n- Verify `git status` is clean\n- Create feature branch: `feat\u002F\u003Cfeature-slug>`\n\n### Step 7: Initialize Scratchpad\nUpdate `.claude\u002Fscratchpad.md` with the full feature context:\n- Feature name and branch\n- Status: \"implementing wave 1 slice 1\u002FN\" (when plan has `Wave:` fields) or \"implementing slice 1\u002FN\" (when no wave assignments)\n- Full plan with slices grouped by wave: each wave as a `### Wave N` subheading with its slices listed as \"pending\". When plan has no `Wave:` fields, list slices as a flat numbered list under `### Wave 1 (sequential)`\n- Empty blockers section\n\nThis is CRITICAL for surviving context compaction during long sessions.\n\n## Output Format\n\n```\n## PRD\n- Section added\u002Fupdated in docs\u002FPRD.md: [section number and title]\n\n## Use Cases\n- Created: docs\u002Fuse-cases\u002F\u003Cfeature>_use_cases.md\n- Primary flows: [count]\n- Alternative flows: [count]\n- Error flows: [count]\n- Edge cases: [count]\n\n## Architecture Review\n- Verdict: PASS\u002FFAIL\n- Action items: [list if any]\n- Slices flagged for security review: [list if any]\n\n## QA Test Cases\n- Created: docs\u002Fqa\u002F\u003Cfeature>_test_cases.md\n- Total test cases: [count]\n- Use-case coverage: [all UC-X mapped \u002F gaps]\n\n## Plan Critique\n- Verdict: PASS (zero BLOCKER findings) \u002F ESCALATED (unresolved BLOCKER after 3 loops) \u002F SKIPPED (plan-critic unresolvable)\n- Loops run: [1-3]\n- Findings: [count] BLOCKER, [count] WARNING, [count] INFO\n- Unresolved BLOCKERs (if escalated): [list]\n\n## Plan (5-9 slices across N waves)\n### Wave 1\n1. [slice description] — covers UC-X.Y\n2. [slice description] — covers UC-X.Z\n\n### Wave 2\n3. [slice description] — covers UC-X.W\n...\n\n## Acceptance Criteria\n- [verifiable condition]\n- ...\n\n## Files to Modify\n- [file paths]\n\n## Git\n- Branch: feat\u002F\u003Cfeature-slug>\n- Base: main\n```\n\n## Constraints\n\n- NEVER skip the PRD step — every feature gets documented first\n- NEVER skip the Use Cases step — all scenarios must be documented\n- NEVER skip the QA step — test cases are documented before code\n- Steps MUST run in order: PRD → Use Cases → Architecture → QA → Plan\n- Follow existing patterns in the codebase\n- Read the project's CLAUDE.md for tech stack and architecture\n","# Command: Bootstrap Feature\n\n## Arguments\n\nThe feature to document is `$feature` (also available as `$ARGUMENTS`). When it is empty, ask the user what to document before Step 1 — do NOT infer a feature from surrounding context.\n\n**Literal-token flag rule:** a documented flag is active ONLY if its literal token appears in `$ARGUMENTS`. Never infer that a flag was passed because the documentation describes it.\n\n## Preflight: Memory Layer Check\n\nRun this FIRST, before Step 1. It takes one Read.\n\n1. Check that `~\u002F.claude\u002Fclaude.md` exists and contains the marker heading `## Autonomous Development Workflow (MANDATORY)`.\n2. If the file is missing, or the marker is absent, print this warning verbatim and **continue anyway**:\n\n   > WARNING: the SDLC memory layer is not installed. `~\u002F.claude\u002Fclaude.md` is missing or does not\n   > contain the pipeline instruction, so the autonomous workflow is not active for unprefixed\n   > requests in this session. Installing the plugin alone is not sufficient — run\n   > `bash install.sh` from the claude-code-sdlc repo to install the memory layer.\n\n3. **Never block on this check.** A missing memory layer degrades autonomy; it does not invalidate this run. Warn once and proceed to Step 1.\n\nKnown limitation: this preflight only fires when this skill is invoked explicitly. An unprefixed natural-language feature request bypasses it entirely, because nothing runs. That gap closes when the SessionStart hook lands (roadmap F2a).\n\n## Agency Documentation Pipeline\n\nEvery feature follows this pipeline before any code is written. Each step is performed by a specialized agent role.\n\n### Step 1: Product Manager — PRD Documentation\nDelegate to `prd-writer` agent:\n- Read `docs\u002FPRD.md` to understand the existing format\n- Add a new section documenting the feature's requirements\n- Include: feature description, user story, functional\u002Fnon-functional requirements, acceptance criteria, affected endpoints, schema changes, UI changes\n\n### Step 2: Business Analyst — Use Cases\nDelegate to `ba-analyst` agent:\n- Read `docs\u002FPRD.md` for the feature requirements just documented\n- Create `docs\u002Fuse-cases\u002F\u003Cfeature-slug>_use_cases.md`\n- Document ALL scenarios: primary flows, alternative flows, error flows, edge cases\n- Include actors, preconditions, postconditions, data requirements\n- This document becomes the blueprint for E2E testing\n\n### Step 3: Software Architect — Architecture Review\nDelegate to `architect` agent:\n- Read PRD and use-case documents\n- Validate the approach against project structure defined in CLAUDE.md\n- Check module boundaries\n- Review any schema changes for data integrity\n- Verify API design follows REST conventions\n- Flag components needing security pre-review during implementation\n\n#### If Architecture Review FAILS:\n1. Read the architect's specific objections\n2. Revise the approach to address each violation\n3. Re-submit to `architect` for review\n4. Retry up to 2 times\n5. If still rejected: document the architectural concern in scratchpad as a blocker and ask the user\n\n### Step 4: QA Lead — Test Case Documentation\nDelegate to `qa-planner` agent:\n- Read `docs\u002FPRD.md` AND `docs\u002Fuse-cases\u002F\u003Cfeature-slug>_use_cases.md`\n- Create `docs\u002Fqa\u002F\u003Cfeature-slug>_test_cases.md`\n- Map every use-case scenario to test cases (UC-1 → TC-1.1, UC-1-E1 → TC-1.2, etc.)\n- Cover: happy path, alternative flows, errors, edge cases, auth boundaries, concurrency\n\n### Step 5: Tech Lead — Implementation Planning\nDelegate to `planner` agent:\n- Read ALL documentation created above: PRD, use cases, architecture review, test cases\n- Read the project's CLAUDE.md for file structure and conventions\n- Break the feature into 5-9 testable implementation slices\n- Each slice references which use-case scenarios it implements (UC-X.Y)\n- Flag slices needing architect or security pre-review\n- Reference actual project files discovered during exploration\n\n#### Step 5a: Plan Critic — Adversarial Plan Review\nAfter the `planner` agent produces the plan and before Step 6 (Git Setup), invoke `plan-critic` against the plan file. This is the first point at which a plan produced entirely by `\u002Fbootstrap-feature` (no interactive plan-mode involved) is critiqued at all.\n\nRun the same critique-and-fix loop `src\u002Fclaude.md`'s plan-mode \"Plan Critic Pass\" section uses:\n1. Invoke `plan-critic` against the plan file (loop 1).\n2. **Fix the plan file for every BLOCKER and every WARNING finding. This fix pass always runs whenever there is at least one BLOCKER or WARNING — it is NOT conditional on a BLOCKER being present.** WARNING is where Scope Reduction Detection lands, and hedging findings must be fixed rather than merely noted.\n2b. **Re-invoke only if a BLOCKER was found** in the loop just completed (loop 2) — the loop repeats on BLOCKERs, the fixing covers WARNINGs too.\n3. Repeat once more if needed (loop 3).\n4. If zero BLOCKER findings remain after any loop, proceed to Step 6 — having already applied the step-2 fixes. Any WARNING deliberately not fixed is recorded with its justification.\n5. If a BLOCKER finding still remains after loop 3, escalate per Rule 4 (`error-recovery.md`): stop, present the remaining BLOCKER findings verbatim, state the decision needed, and present the options. Do NOT proceed to Step 6 with an unresolved BLOCKER.\n\nIf `plan-critic` cannot be resolved (memory-layer-only install with no plugin agents present), warn — naming `plan-critic` explicitly as unresolvable — and proceed to Step 6 without a critique. Never skip the critic pass silently.\n\n### Step 6: Git Setup\n- Verify `git status` is clean\n- Create feature branch: `feat\u002F\u003Cfeature-slug>`\n\n### Step 7: Initialize Scratchpad\nUpdate `.claude\u002Fscratchpad.md` with the full feature context:\n- Feature name and branch\n- Status: \"implementing wave 1 slice 1\u002FN\" (when plan has `Wave:` fields) or \"implementing slice 1\u002FN\" (when no wave assignments)\n- Full plan with slices grouped by wave: each wave as a `### Wave N` subheading with its slices listed as \"pending\". When plan has no `Wave:` fields, list slices as a flat numbered list under `### Wave 1 (sequential)`\n- Empty blockers section\n\nThis is CRITICAL for surviving context compaction during long sessions.\n\n## Output Format\n\n```\n## PRD\n- Section added\u002Fupdated in docs\u002FPRD.md: [section number and title]\n\n## Use Cases\n- Created: docs\u002Fuse-cases\u002F\u003Cfeature>_use_cases.md\n- Primary flows: [count]\n- Alternative flows: [count]\n- Error flows: [count]\n- Edge cases: [count]\n\n## Architecture Review\n- Verdict: PASS\u002FFAIL\n- Action items: [list if any]\n- Slices flagged for security review: [list if any]\n\n## QA Test Cases\n- Created: docs\u002Fqa\u002F\u003Cfeature>_test_cases.md\n- Total test cases: [count]\n- Use-case coverage: [all UC-X mapped \u002F gaps]\n\n## Plan Critique\n- Verdict: PASS (zero BLOCKER findings) \u002F ESCALATED (unresolved BLOCKER after 3 loops) \u002F SKIPPED (plan-critic unresolvable)\n- Loops run: [1-3]\n- Findings: [count] BLOCKER, [count] WARNING, [count] INFO\n- Unresolved BLOCKERs (if escalated): [list]\n\n## Plan (5-9 slices across N waves)\n### Wave 1\n1. [slice description] — covers UC-X.Y\n2. [slice description] — covers UC-X.Z\n\n### Wave 2\n3. [slice description] — covers UC-X.W\n...\n\n## Acceptance Criteria\n- [verifiable condition]\n- ...\n\n## Files to Modify\n- [file paths]\n\n## Git\n- Branch: feat\u002F\u003Cfeature-slug>\n- Base: main\n```\n\n## Constraints\n\n- NEVER skip the PRD step — every feature gets documented first\n- NEVER skip the Use Cases step — all scenarios must be documented\n- NEVER skip the QA step — test cases are documented before code\n- Steps MUST run in order: PRD → Use Cases → Architecture → QA → Plan\n- Follow existing patterns in the codebase\n- Read the project's CLAUDE.md for tech stack and architecture\n",{"arguments":52,"description":7,"allowed-tools":53,"argument-hint":54},[27],"Read, Glob, Grep, Edit, Write, Bash, Agent, TodoWrite","\u003Cfeature description>","main","262994376445c2281eca0784698159bb6e1bf1a3","tests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fbootstrap-feature",3,"https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc","https:\u002F\u002Fgithub.com\u002FKoroqe","https:\u002F\u002Fcone.red\u002Fteam\u002Faleksei-korobeinikov","Co-founder of GetDeal.ai and CONE RED. Author of claude-code-sdlc and OPOS.","2026-10-23 20:51:28",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add Koroqe\u002Fclaude-code-sdlc --skill bootstrap-feature",{"tool":70,"command":71},"bunx","bunx skills add Koroqe\u002Fclaude-code-sdlc --skill bootstrap-feature",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Koroqe\u002Fclaude-code-sdlc --skill bootstrap-feature","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fbootstrap-feature\u002FSKILL.md",true,[],[79,110,127,143,150,159],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":97,"publishedAt":47},"01M6DRTXKTXP8HYDW2G274KAKK","merge-ready","Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI\u002FUX — then write the changelog entry.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fmerge-ready\u002FSKILL.md",[85,90,93,94],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[98,99,100,101,38,45,43,42,102,103,104,105,106,107,108,30,35,34,33,109],"merge","ready","merge ready","code review","git","verification","changelog","ux","audit","doc","security audit","goal",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":47},"01M6DRTT500DJJ8XNQX16037VM","implement-slice","Implement the next smallest slice from the current plan using TDD — tests first, then code, then verification, then an atomic commit. Reads the plan from the scratchpad.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fimplement-slice\u002FSKILL.md",[116],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118,119,120,121,42,103,104,122,30,37,123,35,34,33,124,125,126],"implement","implement slice","tdd","commit","first","grep","next","atomic commit","tests",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":47},"01M6DRTPT1Y4NPEQM56VA4PP0Q","develop-feature","Autonomously implement a complete feature from request to merge-ready — documentation phase, wave-based TDD implementation, then all quality gates, without stopping for human input.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fdevelop-feature\u002FSKILL.md",[],[134,27,135,118,120,98,45,136,30,137,123,35,34,33,99,138,139,140,141,142],"develop","develop feature","quality gates","quality","implementation","human","gates","input","complete",{"skillNo":144,"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":145,"categories":146,"keywords":149,"publishedAt":47},"01M6DRTHJG9KBEG33WNJBRBAFH","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fbootstrap-feature\u002FSKILL.md",[147,148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[29,28,27,38,46,45,44,43,42,41,40,39,30,37,36,35,34,33,32,31],{"skillNo":151,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":158,"publishedAt":47},"01M6DRTDYFS4S3T8MQE4PZHZ7X","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fmerge-ready\u002FSKILL.md",[154,155,156,157],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},[98,99,100,101,38,45,43,42,102,103,104,105,106,107,108,30,35,34,33,109],{"skillNo":160,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":47},"01M6DRTAW68GF6JGNDEWTF6B4V","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fimplement-slice\u002FSKILL.md",[163],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118,119,120,121,42,103,104,122,30,37,123,35,34,33,124,125,126]]