[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQFE6DW9P0PD9AQ687X7E":3,"skill-same:01M70FQFE6DW9P0PD9AQ687X7E":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70FQFE6DW9P0PD9AQ687X7E","configure-ecc",null,"Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user\u002Fproject\u002Flocal) and hook mode (off\u002Fminimal\u002Fstandard\u002Fstrict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under .\u002F.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.","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\u002Fconfigure-ecc\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"configure","configure ecc","preview","setup wizard","when","project surface","mode","hook","native","scope","project","local","run","install","wizard","inventory","lifecycle","collect","harness","code","2026-11-10 10:12:30",false,"---\nname: configure-ecc\ndescription: \"Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user\u002Fproject\u002Flocal) and hook mode (off\u002Fminimal\u002Fstandard\u002Fstrict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under .\u002F.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.\"\nmetadata:\n  origin: ECC\n---\n\n# Configure ECC\n\nRun a conversational wizard inside the current harness. Inventory first, collect\nonly supported choices, preview, confirm once, apply non-interactively, verify,\nand show the welcome only after success. Never clone ECC into a temporary\ndirectory or copy plugin components by hand.\n\nFor a human-operated terminal, the canonical entry points are `ecc setup` and\n`npx ecc-universal setup`. Inside a harness, use the explicit non-interactive\ncommands below instead.\n\n## Route by the current harness\n\n- In Claude Code, use the full scope-and-hook wizard below.\n- In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or\n  map ECC's four Claude hook profiles onto Codex.\n- In Kimi, install the project surface under `.\u002F.kimi-code`. Kimi does not\n  provide ECC's Claude lifecycle-hook profiles.\n- If the harness is uncertain, state the detected evidence and ask which\n  harness to configure before running a mutating command.\n\nThis skill is a post-install reconfiguration path. It cannot intercept or\nreplace a provider's built-in first-install UI.\n\n## Claude Code: run the full conversational wizard\n\n### 1. Inventory without changing anything\n\nRun both commands and summarize the installed ECC scope, enabled state, and\nmarketplace source:\n\n```bash\nclaude plugin list --json\nclaude plugin marketplace list --json\n```\n\nTreat a single existing `ecc@ecc` installation as a reconfiguration. Do not\ninterpret Claude's provider-owned \"Open home page\" control as installation\nevidence. Stop and report the recovery returned by setup for multiple ECC\nscopes, a legacy\u002Fmanual install, malformed settings, or a marketplace collision;\nnever guess which state to delete.\n\n### 2. Collect exactly two choices\n\nAsk exactly one scope question and require one value:\n\n- `user | project | local`\n- `user` is global for this user.\n- `project` is shared through repository settings.\n- `local` is private to the current project.\n\nVisually mark only the selected scope as selected or installing. If the user\nchooses a different scope from a single existing install, describe it as a\nscope migration and include `--move-scope` in the commands below.\n\nAsk exactly one hook-mode question and require one value:\n\n- `off | minimal | standard | strict`\n- `off` keeps skills and commands but disables ECC hook automation.\n- `minimal` enables the lightest lifecycle and safety automation.\n- `standard` balances quality and safety automation.\n- `strict` enables the strongest checks and reminders.\n\nHook preference is personal Claude plugin configuration; it does not follow\nthe selected install scope.\n\n### 3. Preview and confirm once\n\nPrefer the plugin-bundled setup script. Substitute the two selected values and\ninclude `--move-scope` only for a scope migration:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nIf `$CLAUDE_PLUGIN_ROOT` is unavailable, use the published npm package:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nShow exactly one confirmation summary containing the planned action, one scope,\none hook mode, marketplace action, and any source-to-destination migration.\nAsk one yes\u002Fno question. Do not run a bare interactive `ecc setup` through a\nharness shell tool because that shell is commonly non-TTY.\n\n### 4. Apply the explicit choices\n\nAfter confirmation, rerun the same route without `--dry-run`. Keep every choice\nexplicit and request JSON so success can be checked deterministically:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\nFallback:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\n### 5. Verify, then render the welcome\n\nRequire a zero exit status and a setup result whose `scope` and `hooks` equal\nthe selected values. Then independently run:\n\n```bash\nclaude plugin list --json\n```\n\nContinue only when exactly one enabled `ecc@ecc` entry exists at the selected\nscope. When `$CLAUDE_PLUGIN_ROOT` is available, pass the successful setup\n`action` (`installed`, `updated`, `migrated`, `resumed`, or\n`already-migrated`) to the bundled renderer:\n\nBefore invoking it, require the provider-reported version to match\n`ECC_VERSION_PATTERN` from `scripts\u002Flib\u002Fterminal-welcome.js`. Reject unexpected\nversion text instead of interpolating it into a shell command.\n\n```bash\nnode -e 'const { renderTerminalWelcome } = require(process.env.CLAUDE_PLUGIN_ROOT + \"\u002Fscripts\u002Flib\u002Fterminal-welcome\"); process.stdout.write(renderTerminalWelcome({ action: process.argv[1], version: process.argv[2], color: process.stdout.isTTY }));' \"\u003Caction>\" \"\u003Cinstalled-version>\"\n```\n\nRender the welcome exactly once. On failure, dry-run, cancellation, a scope or\nhook mismatch, or unverifiable state, do not render it; report the error and\nrecovery instead. After verified changes, tell the user to run\n`\u002Freload-plugins` or restart Claude Code.\n\n## Codex: use the native plugin lifecycle\n\nInventory with `codex plugin marketplace list --json` and\n`codex plugin list --available --json`. Codex's native plugin command has no\nClaude-style `user | project | local` selector. Codex native plugins do support\nprovider-specific hooks, but Codex requires explicit trust for them. Let Codex\nshow that trust decision; do not ask the Claude four-profile hook question or\nclaim those profiles map to Codex.\n\nIf the ECC marketplace is missing, add it. Otherwise refresh its snapshot:\n\n```bash\ncodex plugin marketplace add affaan-m\u002FECC\ncodex plugin marketplace upgrade ecc --json\n```\n\nAsk for one confirmation, then install or idempotently refresh the installed\ncache and verify it:\n\n```bash\ncodex plugin add ecc@ecc --json\ncodex plugin list --json\n```\n\nContinue only when the JSON reports ECC installed and provides its\n`installedPath`. Then render the verified bundle's welcome:\n\nUse only the exact absolute `installedPath` returned by Codex JSON. Reject\ncontrol characters and require the installed version to match\n`ECC_VERSION_PATTERN`. Invoke `node` directly with this argument array; this is\na tool API invocation, not a shell command:\n\n```text\n[\"\u003CinstalledPath>\u002Fscripts\u002Fwelcome.js\", \"--action\", \"configured\", \"--version\", \"\u003Cinstalled-version>\"]\n```\n\nIf the current harness cannot invoke an executable with a separate argument\narray, skip the welcome. Never construct a shell command from Codex JSON values.\n\nNever claim that Claude's `off | minimal | standard | strict` profiles were\napplied to Codex.\n\n## Kimi: install the project surface\n\nState the capability summary before confirmation: destination\n`.\u002F.kimi-code`; `hooks=unsupported` for ECC lifecycle hooks. Do not ask the\nClaude scope or hook-mode questions. Preview first:\n\n```bash\nnpx --yes --package ecc-universal ecc install --profile core --target kimi --dry-run\n```\n\nShow one confirmation for that project destination, then apply the identical\ncommand without `--dry-run`. Verify with:\n\n```bash\nnpx --yes --package ecc-universal ecc doctor --target kimi\n```\n\nOnly after doctor succeeds and the installed instructions and skills remain\ninside `.\u002F.kimi-code`, render:\n\n```bash\nnpx --yes --package ecc-universal ecc welcome --action configured\n```\n\nDo not claim that Kimi installed or configured ECC lifecycle hooks.\n","# Configure ECC\n\nRun a conversational wizard inside the current harness. Inventory first, collect\nonly supported choices, preview, confirm once, apply non-interactively, verify,\nand show the welcome only after success. Never clone ECC into a temporary\ndirectory or copy plugin components by hand.\n\nFor a human-operated terminal, the canonical entry points are `ecc setup` and\n`npx ecc-universal setup`. Inside a harness, use the explicit non-interactive\ncommands below instead.\n\n## Route by the current harness\n\n- In Claude Code, use the full scope-and-hook wizard below.\n- In Codex, use Codex's native plugin lifecycle. Do not offer Claude scopes or\n  map ECC's four Claude hook profiles onto Codex.\n- In Kimi, install the project surface under `.\u002F.kimi-code`. Kimi does not\n  provide ECC's Claude lifecycle-hook profiles.\n- If the harness is uncertain, state the detected evidence and ask which\n  harness to configure before running a mutating command.\n\nThis skill is a post-install reconfiguration path. It cannot intercept or\nreplace a provider's built-in first-install UI.\n\n## Claude Code: run the full conversational wizard\n\n### 1. Inventory without changing anything\n\nRun both commands and summarize the installed ECC scope, enabled state, and\nmarketplace source:\n\n```bash\nclaude plugin list --json\nclaude plugin marketplace list --json\n```\n\nTreat a single existing `ecc@ecc` installation as a reconfiguration. Do not\ninterpret Claude's provider-owned \"Open home page\" control as installation\nevidence. Stop and report the recovery returned by setup for multiple ECC\nscopes, a legacy\u002Fmanual install, malformed settings, or a marketplace collision;\nnever guess which state to delete.\n\n### 2. Collect exactly two choices\n\nAsk exactly one scope question and require one value:\n\n- `user | project | local`\n- `user` is global for this user.\n- `project` is shared through repository settings.\n- `local` is private to the current project.\n\nVisually mark only the selected scope as selected or installing. If the user\nchooses a different scope from a single existing install, describe it as a\nscope migration and include `--move-scope` in the commands below.\n\nAsk exactly one hook-mode question and require one value:\n\n- `off | minimal | standard | strict`\n- `off` keeps skills and commands but disables ECC hook automation.\n- `minimal` enables the lightest lifecycle and safety automation.\n- `standard` balances quality and safety automation.\n- `strict` enables the strongest checks and reminders.\n\nHook preference is personal Claude plugin configuration; it does not follow\nthe selected install scope.\n\n### 3. Preview and confirm once\n\nPrefer the plugin-bundled setup script. Substitute the two selected values and\ninclude `--move-scope` only for a scope migration:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nIf `$CLAUDE_PLUGIN_ROOT` is unavailable, use the published npm package:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --dry-run --json\n```\n\nShow exactly one confirmation summary containing the planned action, one scope,\none hook mode, marketplace action, and any source-to-destination migration.\nAsk one yes\u002Fno question. Do not run a bare interactive `ecc setup` through a\nharness shell tool because that shell is commonly non-TTY.\n\n### 4. Apply the explicit choices\n\nAfter confirmation, rerun the same route without `--dry-run`. Keep every choice\nexplicit and request JSON so success can be checked deterministically:\n\n```bash\nnode \"$CLAUDE_PLUGIN_ROOT\u002Fscripts\u002Fsetup.js\" --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\nFallback:\n\n```bash\nnpx --yes --package ecc-universal ecc setup --mode claude-plugin \\\n  --scope \u003Cscope> --hooks \u003Chooks> [--move-scope] --yes --json\n```\n\n### 5. Verify, then render the welcome\n\nRequire a zero exit status and a setup result whose `scope` and `hooks` equal\nthe selected values. Then independently run:\n\n```bash\nclaude plugin list --json\n```\n\nContinue only when exactly one enabled `ecc@ecc` entry exists at the selected\nscope. When `$CLAUDE_PLUGIN_ROOT` is available, pass the successful setup\n`action` (`installed`, `updated`, `migrated`, `resumed`, or\n`already-migrated`) to the bundled renderer:\n\nBefore invoking it, require the provider-reported version to match\n`ECC_VERSION_PATTERN` from `scripts\u002Flib\u002Fterminal-welcome.js`. Reject unexpected\nversion text instead of interpolating it into a shell command.\n\n```bash\nnode -e 'const { renderTerminalWelcome } = require(process.env.CLAUDE_PLUGIN_ROOT + \"\u002Fscripts\u002Flib\u002Fterminal-welcome\"); process.stdout.write(renderTerminalWelcome({ action: process.argv[1], version: process.argv[2], color: process.stdout.isTTY }));' \"\u003Caction>\" \"\u003Cinstalled-version>\"\n```\n\nRender the welcome exactly once. On failure, dry-run, cancellation, a scope or\nhook mismatch, or unverifiable state, do not render it; report the error and\nrecovery instead. After verified changes, tell the user to run\n`\u002Freload-plugins` or restart Claude Code.\n\n## Codex: use the native plugin lifecycle\n\nInventory with `codex plugin marketplace list --json` and\n`codex plugin list --available --json`. Codex's native plugin command has no\nClaude-style `user | project | local` selector. Codex native plugins do support\nprovider-specific hooks, but Codex requires explicit trust for them. Let Codex\nshow that trust decision; do not ask the Claude four-profile hook question or\nclaim those profiles map to Codex.\n\nIf the ECC marketplace is missing, add it. Otherwise refresh its snapshot:\n\n```bash\ncodex plugin marketplace add affaan-m\u002FECC\ncodex plugin marketplace upgrade ecc --json\n```\n\nAsk for one confirmation, then install or idempotently refresh the installed\ncache and verify it:\n\n```bash\ncodex plugin add ecc@ecc --json\ncodex plugin list --json\n```\n\nContinue only when the JSON reports ECC installed and provides its\n`installedPath`. Then render the verified bundle's welcome:\n\nUse only the exact absolute `installedPath` returned by Codex JSON. Reject\ncontrol characters and require the installed version to match\n`ECC_VERSION_PATTERN`. Invoke `node` directly with this argument array; this is\na tool API invocation, not a shell command:\n\n```text\n[\"\u003CinstalledPath>\u002Fscripts\u002Fwelcome.js\", \"--action\", \"configured\", \"--version\", \"\u003Cinstalled-version>\"]\n```\n\nIf the current harness cannot invoke an executable with a separate argument\narray, skip the welcome. Never construct a shell command from Codex JSON values.\n\nNever claim that Claude's `off | minimal | standard | strict` profiles were\napplied to Codex.\n\n## Kimi: install the project surface\n\nState the capability summary before confirmation: destination\n`.\u002F.kimi-code`; `hooks=unsupported` for ECC lifecycle hooks. Do not ask the\nClaude scope or hook-mode questions. Preview first:\n\n```bash\nnpx --yes --package ecc-universal ecc install --profile core --target kimi --dry-run\n```\n\nShow one confirmation for that project destination, then apply the identical\ncommand without `--dry-run`. Verify with:\n\n```bash\nnpx --yes --package ecc-universal ecc doctor --target kimi\n```\n\nOnly after doctor succeeds and the installed instructions and skills remain\ninside `.\u002F.kimi-code`, render:\n\n```bash\nnpx --yes --package ecc-universal ecc welcome --action configured\n```\n\nDo not claim that Kimi installed or configured ECC lifecycle hooks.\n",{"name":5,"metadata":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfigure-ecc",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill configure-ecc",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill configure-ecc",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill configure-ecc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfigure-ecc\u002FSKILL.md",true,[],[74,82,90,97,104,111],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"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":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":110,"publishedAt":89},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":89},"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",[],[]]