[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FPVHP0JRE31Y0XVEAJRBZ":3,"skill-same:01M70FPVHP0JRE31Y0XVEAJRBZ":77},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M70FPVHP0JRE31Y0XVEAJRBZ","codehealth-mcp",null,"Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit\u002FPR.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcodehealth-mcp\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"codehealth mcp","MCP","health","file","reviewing code","use","prs","real-time","commits","pr","code quality","refactoring","review","commit","code","when","structural","time","deltas","community","2026-11-10 10:12:30",false,"---\nname: codehealth-mcp\ndescription: Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit\u002FPR.\nmetadata:\n  origin: community\n---\n\n# Code Health MCP (CodeScene)\n\nStructural maintainability feedback for AI-assisted coding. Complements style\u002Flint skills (`coding-standards`, `plankton-code-quality`) with **design-level** health scores and regression gates.\n\n**Upstream:** [codescene-oss\u002Fcodescene-mcp-server](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server)\n**Package:** `@codescene\u002Fcodehealth-mcp` (stdio via npx)\n\n## Security and boundaries\n\n**Opt-in (ECC):** The `codescene` block in `mcp-configs\u002Fmcp-servers.json` is a template only. ECC plugin installs do not auto-enable bundled MCP servers. Copy the entry into your config only if you want it. You can exclude it during ECC install\u002Fsync with `ECC_DISABLED_MCPS=codescene,...`.\n\n**Credentials:** No bundled token. Set `CS_ACCESS_TOKEN` yourself (see [getting-a-personal-access-token.md](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server\u002Fblob\u002Fmain\u002Fdocs\u002Fgetting-a-personal-access-token.md) in the upstream repo). Never commit tokens to the repo.\n\n**What the tools read:** When invoked, tools analyze files and git state **in the local repository** you point them at (paths you pass, plus branch context for `analyze_change_set`). They do not run by themselves. For standalone mode, follow upstream privacy docs: [codescene-mcp-server README](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server#frequently-asked-questions) and [CodeScene policies](https:\u002F\u002Fcodescene.com\u002Fpolicies). Do not use this skill for secrets, credentials, or paths you do not want analyzed.\n\n**If the MCP is unavailable (offline, bad token, server crash):** Do not invent Code Health scores. Tell the user the check was skipped. Continue only with explicit user approval. Prefer lint\u002Ftests\u002Fverification-loop for gating when MCP is down. Re-enable checks once the server connects.\n\n## When to Use\n\n- User asks to **review code quality**, **refactor** a file, or check if **AI changes degraded** maintainability\n- Before editing a **hotspot**, legacy module, or unfamiliar file\n- Before **commit** or **pull request** when you need a maintainability safeguard\n- After a large agent-written diff — verify Code Health did not regress\n- Pair with `verification-loop`, `tdd-workflow`, or `\u002Fquality-gate` as a structural check (not a replacement for tests\u002Flint)\n\n## When to Activate\n\nSame triggers as **When to Use** above — this heading is what ECC uses for skill auto-activation.\n\n## How It Works\n\n### 1. Connect the MCP server\n\nCopy the `codescene` entry from `mcp-configs\u002Fmcp-servers.json` into your harness MCP config.\n\n**Claude Code** (`~\u002F.claude.json` → `mcpServers`):\n\n```json\n\"codescene\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"@codescene\u002Fcodehealth-mcp\"],\n  \"env\": {\n    \"CS_ACCESS_TOKEN\": \"YOUR_CS_ACCESS_TOKEN_HERE\"\n  }\n}\n```\n\n**Project-scoped:** merge the same block into `.mcp.json` at the repo root.\n\nToken setup is documented in the upstream repo (link above). Standalone mode does not require a paid CodeScene platform account for the four tools listed below. Restart the session and confirm the `codescene` server is connected before relying on scores.\n\n### 2. Call standalone tools only\n\n| Tool | When to use |\n|------|-------------|\n| `code_health_review` | Full structural analysis **before** modifying a file |\n| `code_health_score` | Quick numeric score after each change (delta check) |\n| `pre_commit_code_health_safeguard` | Block commits that introduce Code Health regressions |\n| `analyze_change_set` | Branch-level check **before** opening a PR |\n\nDo **not** call platform-only tools (e.g. repository-wide technical debt hotspot lists). Do **not** reference `delta_analysis` — not available on standalone.\n\n### 3. Interpret scores (1–10)\n\n| Range | Meaning | Agent behavior |\n|-------|---------|----------------|\n| **9.0–10.0** | Green — healthy | Safer to extend; still prefer vertical slices |\n| **4.0–8.9** | Yellow — debt | Tread carefully; no drive-by refactors |\n| **1.0–3.9** | Red — severe debt | Narrow scope only |\n\n### 4. Run the feedback loop\n\n**Before touching a file**\n\n1. Run `code_health_review` on the target path.\n2. Record baseline score and listed code smells.\n3. Plan the smallest change that addresses the task.\n\nScope by score: **below 5** — minimal diff only; **5–7** — no broad refactors; **above 7** — safer to refactor, still verify after each edit.\n\n**After each change**\n\n1. Run `code_health_score` on the same file.\n2. Compare to the baseline from `code_health_review`.\n3. If the score **regressed**, fix before continuing. Never mark the task done while the score is lower than when you started.\n\n**Before every commit** — run `pre_commit_code_health_safeguard` on the repository path.\n\n**Before a PR** — run `analyze_change_set` against the base branch (e.g. `main`).\n\n## Examples\n\n### Example: Flask maintainability improvement\n\nOn `pallets\u002Fflask`, an agent loop using only standalone tools:\n\n1. `code_health_review` on a target module (baseline **4.82**)\n2. Targeted refactor addressing listed smells\n3. `code_health_score` after each edit\n4. `pre_commit_code_health_safeguard` before commit\n5. `analyze_change_set` before PR\n\nResult: Code Health **4.82 → 9.1** (free standalone token only).\n\n### Example: AGENTS.md enforcement block\n\nPaste into the project `AGENTS.md` or `CLAUDE.md`:\n\n```md\n## Code Health (CodeScene MCP)\n\nBefore modifying any file: run `code_health_review`, note score and issues.\n\n- Score below 5: problematic range — scope changes narrowly.\n- Score 5–7: warning range — no broad refactors.\n\nAfter each change: run `code_health_score` to verify delta.\n\n- If score regressed: fix before continuing; never declare done if score dropped.\n\nBefore every commit: run `pre_commit_code_health_safeguard`.\n\nBefore PR: run `analyze_change_set`.\n```\n\n### Example: anti-patterns vs correct loop\n\n```markdown\n# BAD: Edit first, check later\n[large refactor without code_health_review]\n\n# BAD: Ignore score drop\n\"Tests pass\" → mark task done while Code Health decreased\n\n# BAD: Broad refactor on red-score file (below 5)\nDrive-by cleanup across the module\n\n# GOOD: review → small change → score → commit safeguard → analyze_change_set\n```\n\n## Pairing with ECC\n\n| ECC skill \u002F flow | Code Health MCP role |\n|------------------|----------------------|\n| `coding-standards` | Style\u002Fnaming; Code Health = structure\u002Fcomplexity |\n| `plankton-code-quality` | Write-time lint\u002Fformat; Code Health = pre\u002Fpost edit structural gate |\n| `verification-loop` \u002F `\u002Fquality-gate` | Add structural regression check before \"done\" |\n| `security-review` | Security vs maintainability — use both when relevant |\n| `tdd-workflow` | Tests pass ≠ healthy design — check score after refactors |\n\n**Context tip:** ECC recommends keeping MCP count low. Enable `codescene` when doing substantive edits; disable when not needed.\n\n## Related Skills\n\n- `coding-standards` — baseline conventions\n- `plankton-code-quality` — write-time lint\u002Fformat hooks\n- `verification-loop` — build\u002Ftest\u002Flint gate\n- `tdd-workflow` — test-first development\n- `security-review` — security checklist\n- `documentation-lookup` — library docs via Context7 (orthogonal)\n","# Code Health MCP (CodeScene)\n\nStructural maintainability feedback for AI-assisted coding. Complements style\u002Flint skills (`coding-standards`, `plankton-code-quality`) with **design-level** health scores and regression gates.\n\n**Upstream:** [codescene-oss\u002Fcodescene-mcp-server](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server)\n**Package:** `@codescene\u002Fcodehealth-mcp` (stdio via npx)\n\n## Security and boundaries\n\n**Opt-in (ECC):** The `codescene` block in `mcp-configs\u002Fmcp-servers.json` is a template only. ECC plugin installs do not auto-enable bundled MCP servers. Copy the entry into your config only if you want it. You can exclude it during ECC install\u002Fsync with `ECC_DISABLED_MCPS=codescene,...`.\n\n**Credentials:** No bundled token. Set `CS_ACCESS_TOKEN` yourself (see [getting-a-personal-access-token.md](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server\u002Fblob\u002Fmain\u002Fdocs\u002Fgetting-a-personal-access-token.md) in the upstream repo). Never commit tokens to the repo.\n\n**What the tools read:** When invoked, tools analyze files and git state **in the local repository** you point them at (paths you pass, plus branch context for `analyze_change_set`). They do not run by themselves. For standalone mode, follow upstream privacy docs: [codescene-mcp-server README](https:\u002F\u002Fgithub.com\u002Fcodescene-oss\u002Fcodescene-mcp-server#frequently-asked-questions) and [CodeScene policies](https:\u002F\u002Fcodescene.com\u002Fpolicies). Do not use this skill for secrets, credentials, or paths you do not want analyzed.\n\n**If the MCP is unavailable (offline, bad token, server crash):** Do not invent Code Health scores. Tell the user the check was skipped. Continue only with explicit user approval. Prefer lint\u002Ftests\u002Fverification-loop for gating when MCP is down. Re-enable checks once the server connects.\n\n## When to Use\n\n- User asks to **review code quality**, **refactor** a file, or check if **AI changes degraded** maintainability\n- Before editing a **hotspot**, legacy module, or unfamiliar file\n- Before **commit** or **pull request** when you need a maintainability safeguard\n- After a large agent-written diff — verify Code Health did not regress\n- Pair with `verification-loop`, `tdd-workflow`, or `\u002Fquality-gate` as a structural check (not a replacement for tests\u002Flint)\n\n## When to Activate\n\nSame triggers as **When to Use** above — this heading is what ECC uses for skill auto-activation.\n\n## How It Works\n\n### 1. Connect the MCP server\n\nCopy the `codescene` entry from `mcp-configs\u002Fmcp-servers.json` into your harness MCP config.\n\n**Claude Code** (`~\u002F.claude.json` → `mcpServers`):\n\n```json\n\"codescene\": {\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"@codescene\u002Fcodehealth-mcp\"],\n  \"env\": {\n    \"CS_ACCESS_TOKEN\": \"YOUR_CS_ACCESS_TOKEN_HERE\"\n  }\n}\n```\n\n**Project-scoped:** merge the same block into `.mcp.json` at the repo root.\n\nToken setup is documented in the upstream repo (link above). Standalone mode does not require a paid CodeScene platform account for the four tools listed below. Restart the session and confirm the `codescene` server is connected before relying on scores.\n\n### 2. Call standalone tools only\n\n| Tool | When to use |\n|------|-------------|\n| `code_health_review` | Full structural analysis **before** modifying a file |\n| `code_health_score` | Quick numeric score after each change (delta check) |\n| `pre_commit_code_health_safeguard` | Block commits that introduce Code Health regressions |\n| `analyze_change_set` | Branch-level check **before** opening a PR |\n\nDo **not** call platform-only tools (e.g. repository-wide technical debt hotspot lists). Do **not** reference `delta_analysis` — not available on standalone.\n\n### 3. Interpret scores (1–10)\n\n| Range | Meaning | Agent behavior |\n|-------|---------|----------------|\n| **9.0–10.0** | Green — healthy | Safer to extend; still prefer vertical slices |\n| **4.0–8.9** | Yellow — debt | Tread carefully; no drive-by refactors |\n| **1.0–3.9** | Red — severe debt | Narrow scope only |\n\n### 4. Run the feedback loop\n\n**Before touching a file**\n\n1. Run `code_health_review` on the target path.\n2. Record baseline score and listed code smells.\n3. Plan the smallest change that addresses the task.\n\nScope by score: **below 5** — minimal diff only; **5–7** — no broad refactors; **above 7** — safer to refactor, still verify after each edit.\n\n**After each change**\n\n1. Run `code_health_score` on the same file.\n2. Compare to the baseline from `code_health_review`.\n3. If the score **regressed**, fix before continuing. Never mark the task done while the score is lower than when you started.\n\n**Before every commit** — run `pre_commit_code_health_safeguard` on the repository path.\n\n**Before a PR** — run `analyze_change_set` against the base branch (e.g. `main`).\n\n## Examples\n\n### Example: Flask maintainability improvement\n\nOn `pallets\u002Fflask`, an agent loop using only standalone tools:\n\n1. `code_health_review` on a target module (baseline **4.82**)\n2. Targeted refactor addressing listed smells\n3. `code_health_score` after each edit\n4. `pre_commit_code_health_safeguard` before commit\n5. `analyze_change_set` before PR\n\nResult: Code Health **4.82 → 9.1** (free standalone token only).\n\n### Example: AGENTS.md enforcement block\n\nPaste into the project `AGENTS.md` or `CLAUDE.md`:\n\n```md\n## Code Health (CodeScene MCP)\n\nBefore modifying any file: run `code_health_review`, note score and issues.\n\n- Score below 5: problematic range — scope changes narrowly.\n- Score 5–7: warning range — no broad refactors.\n\nAfter each change: run `code_health_score` to verify delta.\n\n- If score regressed: fix before continuing; never declare done if score dropped.\n\nBefore every commit: run `pre_commit_code_health_safeguard`.\n\nBefore PR: run `analyze_change_set`.\n```\n\n### Example: anti-patterns vs correct loop\n\n```markdown\n# BAD: Edit first, check later\n[large refactor without code_health_review]\n\n# BAD: Ignore score drop\n\"Tests pass\" → mark task done while Code Health decreased\n\n# BAD: Broad refactor on red-score file (below 5)\nDrive-by cleanup across the module\n\n# GOOD: review → small change → score → commit safeguard → analyze_change_set\n```\n\n## Pairing with ECC\n\n| ECC skill \u002F flow | Code Health MCP role |\n|------------------|----------------------|\n| `coding-standards` | Style\u002Fnaming; Code Health = structure\u002Fcomplexity |\n| `plankton-code-quality` | Write-time lint\u002Fformat; Code Health = pre\u002Fpost edit structural gate |\n| `verification-loop` \u002F `\u002Fquality-gate` | Add structural regression check before \"done\" |\n| `security-review` | Security vs maintainability — use both when relevant |\n| `tdd-workflow` | Tests pass ≠ healthy design — check score after refactors |\n\n**Context tip:** ECC recommends keeping MCP count low. Enable `codescene` when doing substantive edits; disable when not needed.\n\n## Related Skills\n\n- `coding-standards` — baseline conventions\n- `plankton-code-quality` — write-time lint\u002Fformat hooks\n- `verification-loop` — build\u002Ftest\u002Flint gate\n- `tdd-workflow` — test-first development\n- `security-review` — security checklist\n- `documentation-lookup` — library docs via Context7 (orthogonal)\n",{"name":5,"metadata":54,"description":7},{"origin":48},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcodehealth-mcp",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill codehealth-mcp",{"tool":69,"command":70},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill codehealth-mcp",{"tool":72,"command":73},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill codehealth-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcodehealth-mcp\u002FSKILL.md",true,[],[78,86,94,101,108,115],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":92,"publishedAt":93},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":93},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":93},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":93},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":93},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]