[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792GF1DZX8DMXRZ5Z5SC0MR":3,"skill-same:01M792GF1DZX8DMXRZ5Z5SC0MR":61},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M792GF1DZX8DMXRZ5Z5SC0MR","implementation-plan",null,"Break the change into ordered, reviewable steps with checkpoints, so a long task can be stopped and resumed. Use when breaking changes into ordered, testable steps with checkpoints.","poorvith-mp\u002Fskills-developer","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792ACSFXT45RJ69SSGKTVJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fimplementation-plan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementation-plan\nlast_reviewed: 2026-09-06\ngroup: Plan\ndescription: >-\n  Break the change into ordered, reviewable steps with checkpoints, so a long task can be stopped\n  and resumed. Use when breaking changes into ordered, testable steps with checkpoints.\n---\n\n# implementation-plan\n\n## Core Philosophy\nDiving directly into code on complex architectural refactors without a written implementation plan leads to broken builds, forgotten edge cases, scope creep, and irreversible git wreckage. An implementation plan is an engineering blueprint. It breaks complex tasks into ordered, bite-sized increments with testable verification checkpoints at each step—ensuring that long-running work can be stopped, reviewed, and resumed at any time with complete confidence.\n\n---\n\n## 4-Step Implementation Planning Discipline\n\n### Step 1: Scope, Architecture & Dependency Ordering\n1. **Dependency Inversion Ordering**:\n   - Order components logically so that dependencies are created *before* dependents:\n     - 1. Core Data Models \u002F Database Schema Migrations.\n     - 2. Internal Services \u002F Business Logic.\n     - 3. API Endpoints \u002F Controllers.\n     - 4. Frontend UI \u002F Consumer Integration.\n2. **Explicit Non-Goals**:\n   - Clearly delineate what will *not* be built in this iteration to prevent scope creep.\n\n### Step 2: Atomic Phase Breakdown & Checkpoint Design\n1. **The 30-Minute Task Rule**:\n   - Break work down into discrete tasks that take $\\le 30$ minutes to implement and verify.\n2. **Verification Checkpoints**:\n   - Every single task must have an explicit verification step:\n     - \"Run `npm test src\u002Fauth.test.ts` -> Expect 4 passing tests.\"\n     - \"Run `curl -I http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fhealth` -> Expect 200 OK.\"\n\n### Step 3: TDD Integration & Regression Defense\n1. **Test-First Stance**:\n   - Specify the automated test files to be written *before* the implementation code is touched.\n   - Define expected failure conditions (red) and passing criteria (green).\n\n### Step 4: Rollback & Risk Mitigation Protocol\n1. **De-risking Breaking Changes**:\n   - Use the **Expand and Contract (Parallel Run)** pattern for schema and API changes:\n     - Phase 1 (Expand): Add new field\u002Fendpoint; support both old and new.\n     - Phase 2 (Migrate): Shift traffic to new field\u002Fendpoint.\n     - Phase 3 (Contract): Deprecate and remove old field\u002Fendpoint.\n\n---\n\n## Deliverable Format: Implementation Plan Template (`IMPLEMENTATION-PLAN.md`)\n\n```markdown\n# Implementation Plan: [Feature \u002F Refactor Name]\n\n## 1. Overview & Architectural Goal\n[1-2 paragraphs explaining what the change accomplishes and the architectural rationale.]\n\n## 2. Open Questions & Design Decisions\n- [Decision A]: Chosen approach and rationale.\n- [Question B]: Awaiting team clarification.\n\n## 3. Ordered Implementation Phases\n\n### Phase 1: Database & Data Model Layer\n- [ ] **Task 1.1**: Create migration adding `organization_id` column to `users` table.\n  - *Files*: `prisma\u002Fmigrations\u002F20260906_add_org_id.sql`\n  - *Verification*: Run `npx prisma migrate dev` and verify column exists via `psql`.\n- [ ] **Task 1.2**: Update Prisma schema and generate client.\n  - *Files*: `prisma\u002Fschema.prisma`\n  - *Verification*: Run `npx prisma generate` -> builds clean.\n\n### Phase 2: Core Domain Logic & Unit Tests\n- [ ] **Task 2.1 [TDD]**: Write unit tests for OrgMembershipService.\n  - *Files*: `tests\u002Funit\u002Forg-service.test.ts`\n  - *Verification*: Run `npm test tests\u002Funit\u002Forg-service.test.ts` -> Fails (Red).\n- [ ] **Task 2.2**: Implement OrgMembershipService methods.\n  - *Files*: `src\u002Fservices\u002FOrgMembershipService.ts`\n  - *Verification*: Run `npm test tests\u002Funit\u002Forg-service.test.ts` -> Passes (Green).\n\n### Phase 3: API Endpoints & Route Handlers\n- [ ] **Task 3.1**: Expose `POST \u002Fapi\u002Fv1\u002Forganizations\u002F:id\u002Fmembers`.\n  - *Verification*: Execute curl test script against local test server.\n\n## 4. Verification Plan\n- **Automated Tests**: `npm run test:all`\n- **Lint & Types**: `npm run lint && npm run typecheck`\n- **Manual Verification**: End-to-end user invitation flow in local staging browser.\n```\n\n---\n\n## Worked Example: Zero-Downtime Database Migration Plan\n\n- **Refactor**: Split single `User.name` column into `User.firstName` and `User.lastName`.\n- **Phases**:\n  - Phase 1: Added nullable columns `firstName` and `lastName`.\n  - Phase 2: Dual-write to both `name` and new columns in application code.\n  - Phase 3: Background script backfilled historical rows.\n  - Phase 4: Switched reads to `firstName`\u002F`lastName`.\n  - Phase 5: Dropped legacy `name` column.\n- **Outcome**: 100% zero downtime across 5M production records.\n\n---\n\n## Verification Checklist\n\n- [ ] Tasks are arranged in logical dependency order (data -> logic -> API -> UI).\n- [ ] Every individual task includes exact file paths and a verifiable test command.\n- [ ] Explicit non-goals are defined to restrict scope.\n- [ ] TDD unit tests are scheduled prior to implementation tasks.\n- [ ] Rollback strategy is documented for database or API changes.\n\n---\n\n## Anti-Patterns\n\n- **The Monolithic Step**: Writing \"Step 1: Build the backend\" (too vague, impossible to verify incrementally).\n- **Skipping Checkpoints**: Writing 2,000 lines of code across 15 files before running a single test.\n- **Unverified Assumptions**: Proceeding with execution while major architectural questions remain unresolved.\n","# implementation-plan\n\n## Core Philosophy\nDiving directly into code on complex architectural refactors without a written implementation plan leads to broken builds, forgotten edge cases, scope creep, and irreversible git wreckage. An implementation plan is an engineering blueprint. It breaks complex tasks into ordered, bite-sized increments with testable verification checkpoints at each step—ensuring that long-running work can be stopped, reviewed, and resumed at any time with complete confidence.\n\n---\n\n## 4-Step Implementation Planning Discipline\n\n### Step 1: Scope, Architecture & Dependency Ordering\n1. **Dependency Inversion Ordering**:\n   - Order components logically so that dependencies are created *before* dependents:\n     - 1. Core Data Models \u002F Database Schema Migrations.\n     - 2. Internal Services \u002F Business Logic.\n     - 3. API Endpoints \u002F Controllers.\n     - 4. Frontend UI \u002F Consumer Integration.\n2. **Explicit Non-Goals**:\n   - Clearly delineate what will *not* be built in this iteration to prevent scope creep.\n\n### Step 2: Atomic Phase Breakdown & Checkpoint Design\n1. **The 30-Minute Task Rule**:\n   - Break work down into discrete tasks that take $\\le 30$ minutes to implement and verify.\n2. **Verification Checkpoints**:\n   - Every single task must have an explicit verification step:\n     - \"Run `npm test src\u002Fauth.test.ts` -> Expect 4 passing tests.\"\n     - \"Run `curl -I http:\u002F\u002Flocalhost:3000\u002Fapi\u002Fhealth` -> Expect 200 OK.\"\n\n### Step 3: TDD Integration & Regression Defense\n1. **Test-First Stance**:\n   - Specify the automated test files to be written *before* the implementation code is touched.\n   - Define expected failure conditions (red) and passing criteria (green).\n\n### Step 4: Rollback & Risk Mitigation Protocol\n1. **De-risking Breaking Changes**:\n   - Use the **Expand and Contract (Parallel Run)** pattern for schema and API changes:\n     - Phase 1 (Expand): Add new field\u002Fendpoint; support both old and new.\n     - Phase 2 (Migrate): Shift traffic to new field\u002Fendpoint.\n     - Phase 3 (Contract): Deprecate and remove old field\u002Fendpoint.\n\n---\n\n## Deliverable Format: Implementation Plan Template (`IMPLEMENTATION-PLAN.md`)\n\n```markdown\n# Implementation Plan: [Feature \u002F Refactor Name]\n\n## 1. Overview & Architectural Goal\n[1-2 paragraphs explaining what the change accomplishes and the architectural rationale.]\n\n## 2. Open Questions & Design Decisions\n- [Decision A]: Chosen approach and rationale.\n- [Question B]: Awaiting team clarification.\n\n## 3. Ordered Implementation Phases\n\n### Phase 1: Database & Data Model Layer\n- [ ] **Task 1.1**: Create migration adding `organization_id` column to `users` table.\n  - *Files*: `prisma\u002Fmigrations\u002F20260906_add_org_id.sql`\n  - *Verification*: Run `npx prisma migrate dev` and verify column exists via `psql`.\n- [ ] **Task 1.2**: Update Prisma schema and generate client.\n  - *Files*: `prisma\u002Fschema.prisma`\n  - *Verification*: Run `npx prisma generate` -> builds clean.\n\n### Phase 2: Core Domain Logic & Unit Tests\n- [ ] **Task 2.1 [TDD]**: Write unit tests for OrgMembershipService.\n  - *Files*: `tests\u002Funit\u002Forg-service.test.ts`\n  - *Verification*: Run `npm test tests\u002Funit\u002Forg-service.test.ts` -> Fails (Red).\n- [ ] **Task 2.2**: Implement OrgMembershipService methods.\n  - *Files*: `src\u002Fservices\u002FOrgMembershipService.ts`\n  - *Verification*: Run `npm test tests\u002Funit\u002Forg-service.test.ts` -> Passes (Green).\n\n### Phase 3: API Endpoints & Route Handlers\n- [ ] **Task 3.1**: Expose `POST \u002Fapi\u002Fv1\u002Forganizations\u002F:id\u002Fmembers`.\n  - *Verification*: Execute curl test script against local test server.\n\n## 4. Verification Plan\n- **Automated Tests**: `npm run test:all`\n- **Lint & Types**: `npm run lint && npm run typecheck`\n- **Manual Verification**: End-to-end user invitation flow in local staging browser.\n```\n\n---\n\n## Worked Example: Zero-Downtime Database Migration Plan\n\n- **Refactor**: Split single `User.name` column into `User.firstName` and `User.lastName`.\n- **Phases**:\n  - Phase 1: Added nullable columns `firstName` and `lastName`.\n  - Phase 2: Dual-write to both `name` and new columns in application code.\n  - Phase 3: Background script backfilled historical rows.\n  - Phase 4: Switched reads to `firstName`\u002F`lastName`.\n  - Phase 5: Dropped legacy `name` column.\n- **Outcome**: 100% zero downtime across 5M production records.\n\n---\n\n## Verification Checklist\n\n- [ ] Tasks are arranged in logical dependency order (data -> logic -> API -> UI).\n- [ ] Every individual task includes exact file paths and a verifiable test command.\n- [ ] Explicit non-goals are defined to restrict scope.\n- [ ] TDD unit tests are scheduled prior to implementation tasks.\n- [ ] Rollback strategy is documented for database or API changes.\n\n---\n\n## Anti-Patterns\n\n- **The Monolithic Step**: Writing \"Step 1: Build the backend\" (too vague, impossible to verify incrementally).\n- **Skipping Checkpoints**: Writing 2,000 lines of code across 15 files before running a single test.\n- **Unverified Assumptions**: Proceeding with execution while major architectural questions remain unresolved.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Plan",1788652800000,"main","f6a053c46d4bf0f779ea766c929b6f6f92c51765","skills\u002Fimplementation-plan","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add poorvith-mp\u002Fskills-developer --skill implementation-plan",{"tool":41,"command":42},"bunx","bunx skills add poorvith-mp\u002Fskills-developer --skill implementation-plan",{"tool":44,"command":45},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-developer --skill implementation-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fimplementation-plan\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Frouting.yaml","REFERENCE","参考文档",880,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fimplementation-plan\u002Fevals\u002Frouting.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"implementation-plan.skill","OTHER","其他",3193,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fimplementation-plan\u002Fimplementation-plan.skill",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M792Q79X14YD94WXEEJY9GCW","workflow-optimizer","Moved to workflow-mapping in skills-agents. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-optimizer\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M792Q387DNC91VKEVM07SJM3","webhooks","Build webhook receivers with signature verification, idempotency, retries and dead letter queues. Use when implementing, verifying, or signing incoming\u002Foutgoing webhooks.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M792PZW0SM71X7V9709ZWHCR","webhook-handler-builder","Moved to webhooks in skills-developer. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fwebhook-handler-builder\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M792PW7XPB7J9S0QSS52JXZV","voice-ai-integration-engineer","Moved to speech-pipelines in skills-developer. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Fvoice-ai-integration-engineer\u002FSKILL.md",[],[],{"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":19},"01M792PRZ5GSAQ1P2999V9XAJ5","typescript-migrator","Moved to port-code in skills-developer. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-migrator\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":19},"01M792PQDARKP00V8Z3GYD4QZP","trigger-dev","Moved to trigger-dev in skills-agents. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-developer\u002Fblob\u002Fmain\u002Fskills\u002Ftrigger-dev\u002FSKILL.md",[],[]]