[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FTR0122T17B395BDGR244":3,"skill-same:01M70FTR0122T17B395BDGR244":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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70FTR0122T17B395BDGR244","dmux-workflows",null,"Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.","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\u002Fdmux-workflows\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],"dmux workflows","workflows","development","parallel","running","tmux","agent sessions","multi-agent","patterns","development workflows","manager","opencode","across","ai agents","code","when","orchestration","agent orchestration","harnesses","agent development","2026-11-10 10:12:30",false,"---\nname: dmux-workflows\ndescription: Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.\nmetadata:\n  origin: ECC\n---\n\n# dmux Workflows\n\nOrchestrate parallel AI agent sessions using dmux, a tmux pane manager for agent harnesses.\n\n## When to Activate\n\n- Running multiple agent sessions in parallel\n- Coordinating work across Claude Code, Codex, and other harnesses\n- Complex tasks that benefit from divide-and-conquer parallelism\n- User says \"run in parallel\", \"split this work\", \"use dmux\", or \"multi-agent\"\n\n## What is dmux\n\ndmux is a tmux-based orchestration tool that manages AI agent panes:\n- Press `n` to create a new pane with a prompt\n- Press `m` to merge pane output back to the main session\n- Supports: Claude Code, Codex, OpenCode, Cline, Gemini, Qwen\n\n**Install:** Install dmux from its repository after reviewing the package. See [github.com\u002Fstandardagents\u002Fdmux](https:\u002F\u002Fgithub.com\u002Fstandardagents\u002Fdmux)\n\n## Quick Start\n\n```bash\n# Start dmux session\ndmux\n\n# Create agent panes (press 'n' in dmux, then type prompt)\n# Pane 1: \"Implement the auth middleware in src\u002Fauth\u002F\"\n# Pane 2: \"Write tests for the user service\"\n# Pane 3: \"Update API documentation\"\n\n# Each pane runs its own agent session\n# Press 'm' to merge results back\n```\n\n## Workflow Patterns\n\n### Pattern 1: Research + Implement\n\nSplit research and implementation into parallel tracks:\n\n```\nPane 1 (Research): \"Research best practices for rate limiting in Node.js.\n  Check current libraries, compare approaches, and write findings to\n  \u002Ftmp\u002Frate-limit-research.md\"\n\nPane 2 (Implement): \"Implement rate limiting middleware for our Express API.\n  Start with a basic token bucket, we'll refine after research completes.\"\n\n# After Pane 1 completes, merge findings into Pane 2's context\n```\n\n### Pattern 2: Multi-File Feature\n\nParallelize work across independent files:\n\n```\nPane 1: \"Create the database schema and migrations for the billing feature\"\nPane 2: \"Build the billing API endpoints in src\u002Fapi\u002Fbilling\u002F\"\nPane 3: \"Create the billing dashboard UI components\"\n\n# Merge all, then do integration in main pane\n```\n\n### Pattern 3: Test + Fix Loop\n\nRun tests in one pane, fix in another:\n\n```\nPane 1 (Watcher): \"Run the test suite in watch mode. When tests fail,\n  summarize the failures.\"\n\nPane 2 (Fixer): \"Fix failing tests based on the error output from pane 1\"\n```\n\n### Pattern 4: Cross-Harness\n\nUse different AI tools for different tasks:\n\n```\nPane 1 (Claude Code): \"Review the security of the auth module\"\nPane 2 (Codex): \"Refactor the utility functions for performance\"\nPane 3 (Claude Code): \"Write E2E tests for the checkout flow\"\n```\n\n### Pattern 5: Code Review Pipeline\n\nParallel review perspectives:\n\n```\nPane 1: \"Review src\u002Fapi\u002F for security vulnerabilities\"\nPane 2: \"Review src\u002Fapi\u002F for performance issues\"\nPane 3: \"Review src\u002Fapi\u002F for test coverage gaps\"\n\n# Merge all reviews into a single report\n```\n\n## Best Practices\n\n1. **Independent tasks only.** Don't parallelize tasks that depend on each other's output.\n2. **Clear boundaries.** Each pane should work on distinct files or concerns.\n3. **Merge strategically.** Review pane output before merging to avoid conflicts.\n4. **Use git worktrees.** For file-conflict-prone work, use separate worktrees per pane.\n5. **Resource awareness.** Each pane uses API tokens — keep total panes under 5-6.\n\n## Git Worktree Integration\n\nFor tasks that touch overlapping files:\n\n```bash\n# Create worktrees for isolation\ngit worktree add -b feat\u002Fauth ..\u002Ffeature-auth HEAD\ngit worktree add -b feat\u002Fbilling ..\u002Ffeature-billing HEAD\n\n# Run agents in separate worktrees\n# Pane 1: cd ..\u002Ffeature-auth && claude\n# Pane 2: cd ..\u002Ffeature-billing && claude\n\n# Merge branches when done\ngit merge feat\u002Fauth\ngit merge feat\u002Fbilling\n```\n\n## Complementary Tools\n\n| Tool | What It Does | When to Use |\n|------|-------------|-------------|\n| **dmux** | tmux pane management for agents | Parallel agent sessions |\n| **Superset** | Terminal IDE for 10+ parallel agents | Large-scale orchestration |\n| **Claude Code Task tool** | In-process subagent spawning | Programmatic parallelism within a session |\n| **Codex multi-agent** | Built-in agent roles | Codex-specific parallel work |\n\n## ECC Helper\n\nECC now includes a helper for external tmux-pane orchestration with separate git worktrees:\n\n```bash\n# Use the configured plugin root or standalone install (~\u002F.claude or\n# $CLAUDE_CONFIG_DIR). For a reviewed and explicitly authorized ECC checkout:\n# export CLAUDE_PLUGIN_ROOT=\"\u002Fabsolute\u002Fpath\u002Fto\u002Freviewed\u002FECC\"\nECC_ROOT=\"${CLAUDE_PLUGIN_ROOT:-${CLAUDE_CONFIG_DIR:-$HOME\u002F.claude}}\"\n[ -f \"$ECC_ROOT\u002Fscripts\u002Forchestrate-worktrees.js\" ] || { echo \"ECC scripts not found in the selected root (set CLAUDE_PLUGIN_ROOT to an authorized ECC checkout)\" >&2; exit 1; }\nnode \"$ECC_ROOT\u002Fscripts\u002Forchestrate-worktrees.js\" plan.json --execute\n```\n\nExample `plan.json`:\n\n```json\n{\n  \"sessionName\": \"skill-audit\",\n  \"baseRef\": \"HEAD\",\n  \"launcherCommand\": \"codex exec --cwd {worktree_path} --task-file {task_file}\",\n  \"workers\": [\n    { \"name\": \"docs-a\", \"task\": \"Fix skills 1-4 and write handoff notes.\" },\n    { \"name\": \"docs-b\", \"task\": \"Fix skills 5-8 and write handoff notes.\" }\n  ]\n}\n```\n\nThe helper:\n- Creates one branch-backed git worktree per worker\n- Optionally overlays selected `seedPaths` from the main checkout into each worker worktree\n- Writes per-worker `task.md`, `handoff.md`, and `status.md` files under `.orchestration\u002F\u003Csession>\u002F`\n- Starts a tmux session with one pane per worker\n- Launches each worker command in its own pane\n- Leaves the main pane free for the orchestrator\n\nUse `seedPaths` when workers need access to dirty or untracked local files that are not yet part of `HEAD`, such as local orchestration scripts, draft plans, or docs:\n\n```json\n{\n  \"sessionName\": \"workflow-e2e\",\n  \"seedPaths\": [\n    \"scripts\u002Forchestrate-worktrees.js\",\n    \"scripts\u002Flib\u002Ftmux-worktree-orchestrator.js\",\n    \".claude\u002Fplan\u002Fworkflow-e2e-test.json\"\n  ],\n  \"launcherCommand\": \"bash {repo_root}\u002Fscripts\u002Forchestrate-codex-worker.sh {task_file} {handoff_file} {status_file}\",\n  \"workers\": [\n    { \"name\": \"seed-check\", \"task\": \"Verify seeded files are present before starting work.\" }\n  ]\n}\n```\n\n## Troubleshooting\n\n- **Pane not responding:** Switch to the pane directly or inspect it with `tmux capture-pane -pt \u003Csession>:0.\u003Cpane-index>`.\n- **Merge conflicts:** Use git worktrees to isolate file changes per pane.\n- **High token usage:** Reduce number of parallel panes. Each pane is a full agent session.\n- **tmux not found:** Install with `brew install tmux` (macOS) or `apt install tmux` (Linux).\n","# dmux Workflows\n\nOrchestrate parallel AI agent sessions using dmux, a tmux pane manager for agent harnesses.\n\n## When to Activate\n\n- Running multiple agent sessions in parallel\n- Coordinating work across Claude Code, Codex, and other harnesses\n- Complex tasks that benefit from divide-and-conquer parallelism\n- User says \"run in parallel\", \"split this work\", \"use dmux\", or \"multi-agent\"\n\n## What is dmux\n\ndmux is a tmux-based orchestration tool that manages AI agent panes:\n- Press `n` to create a new pane with a prompt\n- Press `m` to merge pane output back to the main session\n- Supports: Claude Code, Codex, OpenCode, Cline, Gemini, Qwen\n\n**Install:** Install dmux from its repository after reviewing the package. See [github.com\u002Fstandardagents\u002Fdmux](https:\u002F\u002Fgithub.com\u002Fstandardagents\u002Fdmux)\n\n## Quick Start\n\n```bash\n# Start dmux session\ndmux\n\n# Create agent panes (press 'n' in dmux, then type prompt)\n# Pane 1: \"Implement the auth middleware in src\u002Fauth\u002F\"\n# Pane 2: \"Write tests for the user service\"\n# Pane 3: \"Update API documentation\"\n\n# Each pane runs its own agent session\n# Press 'm' to merge results back\n```\n\n## Workflow Patterns\n\n### Pattern 1: Research + Implement\n\nSplit research and implementation into parallel tracks:\n\n```\nPane 1 (Research): \"Research best practices for rate limiting in Node.js.\n  Check current libraries, compare approaches, and write findings to\n  \u002Ftmp\u002Frate-limit-research.md\"\n\nPane 2 (Implement): \"Implement rate limiting middleware for our Express API.\n  Start with a basic token bucket, we'll refine after research completes.\"\n\n# After Pane 1 completes, merge findings into Pane 2's context\n```\n\n### Pattern 2: Multi-File Feature\n\nParallelize work across independent files:\n\n```\nPane 1: \"Create the database schema and migrations for the billing feature\"\nPane 2: \"Build the billing API endpoints in src\u002Fapi\u002Fbilling\u002F\"\nPane 3: \"Create the billing dashboard UI components\"\n\n# Merge all, then do integration in main pane\n```\n\n### Pattern 3: Test + Fix Loop\n\nRun tests in one pane, fix in another:\n\n```\nPane 1 (Watcher): \"Run the test suite in watch mode. When tests fail,\n  summarize the failures.\"\n\nPane 2 (Fixer): \"Fix failing tests based on the error output from pane 1\"\n```\n\n### Pattern 4: Cross-Harness\n\nUse different AI tools for different tasks:\n\n```\nPane 1 (Claude Code): \"Review the security of the auth module\"\nPane 2 (Codex): \"Refactor the utility functions for performance\"\nPane 3 (Claude Code): \"Write E2E tests for the checkout flow\"\n```\n\n### Pattern 5: Code Review Pipeline\n\nParallel review perspectives:\n\n```\nPane 1: \"Review src\u002Fapi\u002F for security vulnerabilities\"\nPane 2: \"Review src\u002Fapi\u002F for performance issues\"\nPane 3: \"Review src\u002Fapi\u002F for test coverage gaps\"\n\n# Merge all reviews into a single report\n```\n\n## Best Practices\n\n1. **Independent tasks only.** Don't parallelize tasks that depend on each other's output.\n2. **Clear boundaries.** Each pane should work on distinct files or concerns.\n3. **Merge strategically.** Review pane output before merging to avoid conflicts.\n4. **Use git worktrees.** For file-conflict-prone work, use separate worktrees per pane.\n5. **Resource awareness.** Each pane uses API tokens — keep total panes under 5-6.\n\n## Git Worktree Integration\n\nFor tasks that touch overlapping files:\n\n```bash\n# Create worktrees for isolation\ngit worktree add -b feat\u002Fauth ..\u002Ffeature-auth HEAD\ngit worktree add -b feat\u002Fbilling ..\u002Ffeature-billing HEAD\n\n# Run agents in separate worktrees\n# Pane 1: cd ..\u002Ffeature-auth && claude\n# Pane 2: cd ..\u002Ffeature-billing && claude\n\n# Merge branches when done\ngit merge feat\u002Fauth\ngit merge feat\u002Fbilling\n```\n\n## Complementary Tools\n\n| Tool | What It Does | When to Use |\n|------|-------------|-------------|\n| **dmux** | tmux pane management for agents | Parallel agent sessions |\n| **Superset** | Terminal IDE for 10+ parallel agents | Large-scale orchestration |\n| **Claude Code Task tool** | In-process subagent spawning | Programmatic parallelism within a session |\n| **Codex multi-agent** | Built-in agent roles | Codex-specific parallel work |\n\n## ECC Helper\n\nECC now includes a helper for external tmux-pane orchestration with separate git worktrees:\n\n```bash\n# Use the configured plugin root or standalone install (~\u002F.claude or\n# $CLAUDE_CONFIG_DIR). For a reviewed and explicitly authorized ECC checkout:\n# export CLAUDE_PLUGIN_ROOT=\"\u002Fabsolute\u002Fpath\u002Fto\u002Freviewed\u002FECC\"\nECC_ROOT=\"${CLAUDE_PLUGIN_ROOT:-${CLAUDE_CONFIG_DIR:-$HOME\u002F.claude}}\"\n[ -f \"$ECC_ROOT\u002Fscripts\u002Forchestrate-worktrees.js\" ] || { echo \"ECC scripts not found in the selected root (set CLAUDE_PLUGIN_ROOT to an authorized ECC checkout)\" >&2; exit 1; }\nnode \"$ECC_ROOT\u002Fscripts\u002Forchestrate-worktrees.js\" plan.json --execute\n```\n\nExample `plan.json`:\n\n```json\n{\n  \"sessionName\": \"skill-audit\",\n  \"baseRef\": \"HEAD\",\n  \"launcherCommand\": \"codex exec --cwd {worktree_path} --task-file {task_file}\",\n  \"workers\": [\n    { \"name\": \"docs-a\", \"task\": \"Fix skills 1-4 and write handoff notes.\" },\n    { \"name\": \"docs-b\", \"task\": \"Fix skills 5-8 and write handoff notes.\" }\n  ]\n}\n```\n\nThe helper:\n- Creates one branch-backed git worktree per worker\n- Optionally overlays selected `seedPaths` from the main checkout into each worker worktree\n- Writes per-worker `task.md`, `handoff.md`, and `status.md` files under `.orchestration\u002F\u003Csession>\u002F`\n- Starts a tmux session with one pane per worker\n- Launches each worker command in its own pane\n- Leaves the main pane free for the orchestrator\n\nUse `seedPaths` when workers need access to dirty or untracked local files that are not yet part of `HEAD`, such as local orchestration scripts, draft plans, or docs:\n\n```json\n{\n  \"sessionName\": \"workflow-e2e\",\n  \"seedPaths\": [\n    \"scripts\u002Forchestrate-worktrees.js\",\n    \"scripts\u002Flib\u002Ftmux-worktree-orchestrator.js\",\n    \".claude\u002Fplan\u002Fworkflow-e2e-test.json\"\n  ],\n  \"launcherCommand\": \"bash {repo_root}\u002Fscripts\u002Forchestrate-codex-worker.sh {task_file} {handoff_file} {status_file}\",\n  \"workers\": [\n    { \"name\": \"seed-check\", \"task\": \"Verify seeded files are present before starting work.\" }\n  ]\n}\n```\n\n## Troubleshooting\n\n- **Pane not responding:** Switch to the pane directly or inspect it with `tmux capture-pane -pt \u003Csession>:0.\u003Cpane-index>`.\n- **Merge conflicts:** Use git worktrees to isolate file changes per pane.\n- **High token usage:** Reduce number of parallel panes. Each pane is a full agent session.\n- **tmux not found:** Install with `brew install tmux` (macOS) or `apt install tmux` (Linux).\n",{"name":5,"metadata":54,"description":7},{"origin":55},"ECC","main","7092b664627bf326748a6fcbf27fee6a34c4da1d","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fdmux-workflows",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill dmux-workflows",{"tool":70,"command":71},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill dmux-workflows",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill dmux-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdmux-workflows\u002FSKILL.md",true,[],[79,87,95,102,109,116],{"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":85,"publishedAt":86},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":94},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":94},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":94},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":94},"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",[],[]]