[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CA8KD2R50J0DVPC0RFAS3F":3,"skill-same:01M7CA8KD2R50J0DVPC0RFAS3F":66},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CA8KD2R50J0DVPC0RFAS3F","parallel-feature-development",null,"Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature.","Pu11en\u002Febi-agent-chat-relay","Pu11en","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F111389815?v=4","01M7CA7FFK3WN6Y7CFYQ3TX73Q","Drew Pullen","01M7CA7FG6W1N47BR1D5HTT53G",1,"MIT","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fparallel-feature-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fparallel-feature-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: parallel-feature-development\ndescription: Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system simultaneously, when establishing file ownership to prevent merge conflicts in a shared codebase, when designing interface contracts so parallel implementers can build against each other's APIs before they are ready, or when deciding whether to use vertical slices versus horizontal layers for a full-stack feature.\nversion: 1.0.2\n---\n\n# Parallel Feature Development\n\nStrategies for decomposing features into parallel work streams, establishing file ownership boundaries, avoiding conflicts, and integrating results from multiple implementer agents.\n\n## When to Use This Skill\n\n- Decomposing a feature for parallel implementation\n- Establishing file ownership boundaries between agents\n- Designing interface contracts between parallel work streams\n- Choosing integration strategies (vertical slice vs horizontal layer)\n- Managing branch and merge workflows for parallel development\n\n## File Ownership Strategies\n\n### By Directory\n\nAssign each implementer ownership of specific directories:\n\n```\nimplementer-1: src\u002Fcomponents\u002Fauth\u002F\nimplementer-2: src\u002Fapi\u002Fauth\u002F\nimplementer-3: tests\u002Fauth\u002F\n```\n\n**Best for**: Well-organized codebases with clear directory boundaries.\n\n### By Module\n\nAssign ownership of logical modules (which may span directories):\n\n```\nimplementer-1: Authentication module (login, register, logout)\nimplementer-2: Authorization module (roles, permissions, guards)\n```\n\n**Best for**: Feature-oriented architectures, domain-driven design.\n\n### By Layer\n\nAssign ownership of architectural layers:\n\n```\nimplementer-1: UI layer (components, styles, layouts)\nimplementer-2: Business logic layer (services, validators)\nimplementer-3: Data layer (models, repositories, migrations)\n```\n\n**Best for**: Traditional MVC\u002Flayered architectures.\n\n## Conflict Avoidance Rules\n\n### The Cardinal Rule\n\n**One owner per file.** No file should be assigned to multiple implementers.\n\n### When Files Must Be Shared\n\nIf a file genuinely needs changes from multiple implementers:\n\n1. **Designate a single owner** — One implementer owns the file\n2. **Other implementers request changes** — Message the owner with specific change requests\n3. **Owner applies changes sequentially** — Prevents merge conflicts\n4. **Alternative: Extract interfaces** — Create a separate interface file that the non-owner can import without modifying\n\n### Interface Contracts\n\nWhen implementers need to coordinate at boundaries:\n\n```typescript\n\u002F\u002F src\u002Ftypes\u002Fauth-contract.ts (owned by team-lead, read-only for implementers)\nexport interface AuthResponse {\n  token: string;\n  user: UserProfile;\n  expiresAt: number;\n}\n\nexport interface AuthService {\n  login(email: string, password: string): Promise\u003CAuthResponse>;\n  register(data: RegisterData): Promise\u003CAuthResponse>;\n}\n```\n\nBoth implementers import from the contract file but neither modifies it.\n\n## Integration Patterns\n\n### Vertical Slice\n\nEach implementer builds a complete feature slice (UI + API + tests):\n\n```\nimplementer-1: Login feature (login form + login API + login tests)\nimplementer-2: Register feature (register form + register API + register tests)\n```\n\n**Pros**: Each slice is independently testable, minimal integration needed.\n**Cons**: May duplicate shared utilities, harder with tightly coupled features.\n\n### Horizontal Layer\n\nEach implementer builds one layer across all features:\n\n```\nimplementer-1: All UI components (login form, register form, profile page)\nimplementer-2: All API endpoints (login, register, profile)\nimplementer-3: All tests (unit, integration, e2e)\n```\n\n**Pros**: Consistent patterns within each layer, natural specialization.\n**Cons**: More integration points, layer 3 depends on layers 1 and 2.\n\n### Hybrid\n\nMix vertical and horizontal based on coupling:\n\n```\nimplementer-1: Login feature (vertical slice — UI + API + tests)\nimplementer-2: Shared auth infrastructure (horizontal — middleware, JWT utils, types)\n```\n\n**Best for**: Most real-world features with some shared infrastructure.\n\n## Branch Management\n\n### Single Branch Strategy\n\nAll implementers work on the same feature branch:\n\n- Simple setup, no merge overhead\n- Requires strict file ownership to avoid conflicts\n- Best for: small teams (2-3), well-defined boundaries\n\n### Multi-Branch Strategy\n\nEach implementer works on a sub-branch:\n\n```\nfeature\u002Fauth\n  ├── feature\u002Fauth-login      (implementer-1)\n  ├── feature\u002Fauth-register    (implementer-2)\n  └── feature\u002Fauth-tests       (implementer-3)\n```\n\n- More isolation, explicit merge points\n- Higher overhead, merge conflicts still possible in shared files\n- Best for: larger teams (4+), complex features\n\n## Troubleshooting\n\n**Implementers are blocking each other waiting for shared code.**\nExtract the shared piece into its own interface contract file owned by the team-lead and have implementers import from it. Neither implementer modifies the contract — they only implement against it.\n\n**Merge conflicts appear even with clear ownership rules.**\nA file was assigned to two agents, or a config\u002Findex file (e.g., `index.ts`, `__init__.py`) that auto-imports everything was modified by both. Designate one owner for all barrel\u002Findex files, or have the lead merge them at the end.\n\n**An implementer finishes early but the integration step is blocked.**\nUse a staging interface: the finished implementer writes a stub or mock of the downstream dependency so the other implementer can continue working. Replace with the real implementation at integration time.\n\n**The feature decomposition turned out wrong mid-stream.**\nStop new work, have the lead redistribute files, and communicate the change via broadcast. Sunk cost on partially written code is acceptable — continuing with the wrong split is worse.\n\n**Tests written by one implementer fail against code written by another.**\nInterface contracts drifted: the implementer who owns the API changed a signature without notifying the test implementer. Enforce the rule that contract files require a broadcast before modification.\n\n## Related Skills\n\n- [team-composition-patterns](..\u002Fteam-composition-patterns\u002FSKILL.md) — Choose the right team size and agent types before decomposing work\n- [team-communication-protocols](..\u002Fteam-communication-protocols\u002FSKILL.md) — Coordinate integration handoffs and plan approvals between implementers\n","# Parallel Feature Development\n\nStrategies for decomposing features into parallel work streams, establishing file ownership boundaries, avoiding conflicts, and integrating results from multiple implementer agents.\n\n## When to Use This Skill\n\n- Decomposing a feature for parallel implementation\n- Establishing file ownership boundaries between agents\n- Designing interface contracts between parallel work streams\n- Choosing integration strategies (vertical slice vs horizontal layer)\n- Managing branch and merge workflows for parallel development\n\n## File Ownership Strategies\n\n### By Directory\n\nAssign each implementer ownership of specific directories:\n\n```\nimplementer-1: src\u002Fcomponents\u002Fauth\u002F\nimplementer-2: src\u002Fapi\u002Fauth\u002F\nimplementer-3: tests\u002Fauth\u002F\n```\n\n**Best for**: Well-organized codebases with clear directory boundaries.\n\n### By Module\n\nAssign ownership of logical modules (which may span directories):\n\n```\nimplementer-1: Authentication module (login, register, logout)\nimplementer-2: Authorization module (roles, permissions, guards)\n```\n\n**Best for**: Feature-oriented architectures, domain-driven design.\n\n### By Layer\n\nAssign ownership of architectural layers:\n\n```\nimplementer-1: UI layer (components, styles, layouts)\nimplementer-2: Business logic layer (services, validators)\nimplementer-3: Data layer (models, repositories, migrations)\n```\n\n**Best for**: Traditional MVC\u002Flayered architectures.\n\n## Conflict Avoidance Rules\n\n### The Cardinal Rule\n\n**One owner per file.** No file should be assigned to multiple implementers.\n\n### When Files Must Be Shared\n\nIf a file genuinely needs changes from multiple implementers:\n\n1. **Designate a single owner** — One implementer owns the file\n2. **Other implementers request changes** — Message the owner with specific change requests\n3. **Owner applies changes sequentially** — Prevents merge conflicts\n4. **Alternative: Extract interfaces** — Create a separate interface file that the non-owner can import without modifying\n\n### Interface Contracts\n\nWhen implementers need to coordinate at boundaries:\n\n```typescript\n\u002F\u002F src\u002Ftypes\u002Fauth-contract.ts (owned by team-lead, read-only for implementers)\nexport interface AuthResponse {\n  token: string;\n  user: UserProfile;\n  expiresAt: number;\n}\n\nexport interface AuthService {\n  login(email: string, password: string): Promise\u003CAuthResponse>;\n  register(data: RegisterData): Promise\u003CAuthResponse>;\n}\n```\n\nBoth implementers import from the contract file but neither modifies it.\n\n## Integration Patterns\n\n### Vertical Slice\n\nEach implementer builds a complete feature slice (UI + API + tests):\n\n```\nimplementer-1: Login feature (login form + login API + login tests)\nimplementer-2: Register feature (register form + register API + register tests)\n```\n\n**Pros**: Each slice is independently testable, minimal integration needed.\n**Cons**: May duplicate shared utilities, harder with tightly coupled features.\n\n### Horizontal Layer\n\nEach implementer builds one layer across all features:\n\n```\nimplementer-1: All UI components (login form, register form, profile page)\nimplementer-2: All API endpoints (login, register, profile)\nimplementer-3: All tests (unit, integration, e2e)\n```\n\n**Pros**: Consistent patterns within each layer, natural specialization.\n**Cons**: More integration points, layer 3 depends on layers 1 and 2.\n\n### Hybrid\n\nMix vertical and horizontal based on coupling:\n\n```\nimplementer-1: Login feature (vertical slice — UI + API + tests)\nimplementer-2: Shared auth infrastructure (horizontal — middleware, JWT utils, types)\n```\n\n**Best for**: Most real-world features with some shared infrastructure.\n\n## Branch Management\n\n### Single Branch Strategy\n\nAll implementers work on the same feature branch:\n\n- Simple setup, no merge overhead\n- Requires strict file ownership to avoid conflicts\n- Best for: small teams (2-3), well-defined boundaries\n\n### Multi-Branch Strategy\n\nEach implementer works on a sub-branch:\n\n```\nfeature\u002Fauth\n  ├── feature\u002Fauth-login      (implementer-1)\n  ├── feature\u002Fauth-register    (implementer-2)\n  └── feature\u002Fauth-tests       (implementer-3)\n```\n\n- More isolation, explicit merge points\n- Higher overhead, merge conflicts still possible in shared files\n- Best for: larger teams (4+), complex features\n\n## Troubleshooting\n\n**Implementers are blocking each other waiting for shared code.**\nExtract the shared piece into its own interface contract file owned by the team-lead and have implementers import from it. Neither implementer modifies the contract — they only implement against it.\n\n**Merge conflicts appear even with clear ownership rules.**\nA file was assigned to two agents, or a config\u002Findex file (e.g., `index.ts`, `__init__.py`) that auto-imports everything was modified by both. Designate one owner for all barrel\u002Findex files, or have the lead merge them at the end.\n\n**An implementer finishes early but the integration step is blocked.**\nUse a staging interface: the finished implementer writes a stub or mock of the downstream dependency so the other implementer can continue working. Replace with the real implementation at integration time.\n\n**The feature decomposition turned out wrong mid-stream.**\nStop new work, have the lead redistribute files, and communicate the change via broadcast. Sunk cost on partially written code is acceptable — continuing with the wrong split is worse.\n\n**Tests written by one implementer fail against code written by another.**\nInterface contracts drifted: the implementer who owns the API changed a signature without notifying the test implementer. Enforce the rule that contract files require a broadcast before modification.\n\n## Related Skills\n\n- [team-composition-patterns](..\u002Fteam-composition-patterns\u002FSKILL.md) — Choose the right team size and agent types before decomposing work\n- [team-communication-protocols](..\u002Fteam-communication-protocols\u002FSKILL.md) — Coordinate integration handoffs and plan approvals between implementers\n",{"name":5,"version":25,"description":7},"1.0.2","main","1514f26de05c299ab3e67d8d34e3974fb1caad16",".agents\u002Fskills\u002Fparallel-feature-development",0,"https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay","https:\u002F\u002Fgithub.com\u002FPu11en","na","2026-11-02 10:19:54",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Pu11en\u002Febi-agent-chat-relay --skill parallel-feature-development",{"tool":40,"command":41},"bunx","bunx skills add Pu11en\u002Febi-agent-chat-relay --skill parallel-feature-development",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Pu11en\u002Febi-agent-chat-relay --skill parallel-feature-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fparallel-feature-development\u002FSKILL.md",true,[48,52,58,62],{"path":49,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Ffile-ownership.md","REFERENCE","参考文档",2460,"https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fparallel-feature-development\u002Freferences\u002Ffile-ownership.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmerge-strategies.md",2342,"https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fparallel-feature-development\u002Freferences\u002Fmerge-strategies.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"SOURCE.json",586,"https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fparallel-feature-development\u002FSOURCE.json",[67,74,81,86,91,98],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M7CA9RN8X1AQA6NCMF5HTM70","release","Cut a release","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_audit\u002Fimac\u002Fhome\u002F.codex\u002Fskills\u002Frelease\u002FSKILL.md",[],[],{"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":20},"01M7CA9QPA81A7X517Z0TV8JP6","deploy","Deploy the bot","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_audit\u002Fimac\u002Fhome\u002F.claude\u002Fskills\u002Fdeploy\u002FSKILL.md",[],[],{"skillNo":82,"name":69,"nameZh":6,"description":70,"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":20},"01M7CA9PQNYWC52KPANCHESMR4","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_audit\u002Fdrewai\u002Fhome\u002F.codex\u002Fskills\u002Frelease\u002FSKILL.md",[],[],{"skillNo":87,"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":88,"categories":89,"keywords":90,"publishedAt":20},"01M7CA9NFB9PAPRP4RDNT6RE12","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fharness_audit\u002Fdrewai\u002Fhome\u002F.claude\u002Fskills\u002Fdeploy\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M7CA9HYXBKV4GGD372K0QWX8","lockin-feature-workflow","Plan distinct features with OpenSpec in Lockin AI Discord conversations, split clearly independent builds into linked child planning threads, or dispatch every approved dependency-ready task to visible Ebi workers and integrate their results through one owner. Use for feature planning, approved parallel builds, and resuming a coordinated build.","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002Fextensions\u002Ffeature_workflow\u002Fskill\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M7CA9DWY01WPNSKG9ZM0T4E2","master-planning","Guide project brainstorming, clarify requirements through short questions, and turn agreed decisions into coordinated plans for fresh-session builders. Use for planning a project, business, feature, or several related build lanes; resume when the user answers an active planning question. Do not invoke for an already scoped small fix, a factual question, or executing an existing plan.","https:\u002F\u002Fgithub.com\u002FPu11en\u002Febi-agent-chat-relay\u002Fblob\u002Fmain\u002F.planning\u002Fgowork-flow\u002Fplanner-skill-draft\u002FSKILL.md",[],[]]