[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YSWXDFZA57TM8AP8BSBFY":3,"skill-same:01M72YSWXDFZA57TM8AP8BSBFY":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72YSWXDFZA57TM8AP8BSBFY","project-flow-ops",null,"Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fskills\u002Fproject-flow-ops\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: project-flow-ops\ndescription: Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.\norigin: ECC\n---\n\n# Project Flow Ops\n\nThis skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.\n\nUse it when the problem is coordination, not coding.\n\n## When to Use\n\n- Triage open PR or issue backlogs\n- Decide what belongs in Linear vs what should remain GitHub-only\n- Link active GitHub work to internal execution lanes\n- Classify PRs into merge, port\u002Frebuild, close, or park\n- Audit whether review comments, CI failures, or stale issues are blocking execution\n\n## Operating Model\n\n- **GitHub** is the public and community truth\n- **Linear** is the internal execution truth for active scheduled work\n- Not every GitHub issue needs a Linear issue\n- Create or update Linear only when the work is:\n  - active\n  - delegated\n  - scheduled\n  - cross-functional\n  - important enough to track internally\n\n## Core Workflow\n\n### 1. Read the public surface first\n\nGather:\n\n- GitHub issue or PR state\n- author and branch status\n- review comments\n- CI status\n- linked issues\n\n### 2. Classify the work\n\nEvery item should end up in one of these states:\n\n| State | Meaning |\n|-------|---------|\n| Merge | self-contained, policy-compliant, ready |\n| Port\u002FRebuild | useful idea, but should be manually re-landed inside ECC |\n| Close | wrong direction, stale, unsafe, or duplicated |\n| Park | potentially useful, but not scheduled now |\n\n### 3. Decide whether Linear is warranted\n\nCreate or update Linear only if:\n\n- execution is actively planned\n- multiple repos or workstreams are involved\n- the work needs internal ownership or sequencing\n- the issue is part of a larger program lane\n\nDo not mirror everything mechanically.\n\n### 4. Keep the two systems consistent\n\nWhen work is active:\n\n- GitHub issue\u002FPR should say what is happening publicly\n- Linear should track owner, priority, and execution lane internally\n\nWhen work ships or is rejected:\n\n- post the public resolution back to GitHub\n- mark the Linear task accordingly\n\n## Review Rules\n\n- Never merge from title, summary, or trust alone; use the full diff\n- External-source features should be rebuilt inside ECC when they are valuable but not self-contained\n- CI red means classify and fix or block; do not pretend it is merge-ready\n- If the real blocker is product direction, say so instead of hiding behind tooling\n\n## Output Format\n\nReturn:\n\n```text\nPUBLIC STATUS\n- issue \u002F PR state\n- CI \u002F review state\n\nCLASSIFICATION\n- merge \u002F port-rebuild \u002F close \u002F park\n- one-paragraph rationale\n\nLINEAR ACTION\n- create \u002F update \u002F no Linear item needed\n- project \u002F lane if applicable\n\nNEXT OPERATOR ACTION\n- exact next move\n```\n\n## Good Use Cases\n\n- \"Audit the open PR backlog and tell me what to merge vs rebuild\"\n- \"Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes\"\n- \"Check whether this needs a Linear issue or should stay GitHub-only\"\n","# Project Flow Ops\n\nThis skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.\n\nUse it when the problem is coordination, not coding.\n\n## When to Use\n\n- Triage open PR or issue backlogs\n- Decide what belongs in Linear vs what should remain GitHub-only\n- Link active GitHub work to internal execution lanes\n- Classify PRs into merge, port\u002Frebuild, close, or park\n- Audit whether review comments, CI failures, or stale issues are blocking execution\n\n## Operating Model\n\n- **GitHub** is the public and community truth\n- **Linear** is the internal execution truth for active scheduled work\n- Not every GitHub issue needs a Linear issue\n- Create or update Linear only when the work is:\n  - active\n  - delegated\n  - scheduled\n  - cross-functional\n  - important enough to track internally\n\n## Core Workflow\n\n### 1. Read the public surface first\n\nGather:\n\n- GitHub issue or PR state\n- author and branch status\n- review comments\n- CI status\n- linked issues\n\n### 2. Classify the work\n\nEvery item should end up in one of these states:\n\n| State | Meaning |\n|-------|---------|\n| Merge | self-contained, policy-compliant, ready |\n| Port\u002FRebuild | useful idea, but should be manually re-landed inside ECC |\n| Close | wrong direction, stale, unsafe, or duplicated |\n| Park | potentially useful, but not scheduled now |\n\n### 3. Decide whether Linear is warranted\n\nCreate or update Linear only if:\n\n- execution is actively planned\n- multiple repos or workstreams are involved\n- the work needs internal ownership or sequencing\n- the issue is part of a larger program lane\n\nDo not mirror everything mechanically.\n\n### 4. Keep the two systems consistent\n\nWhen work is active:\n\n- GitHub issue\u002FPR should say what is happening publicly\n- Linear should track owner, priority, and execution lane internally\n\nWhen work ships or is rejected:\n\n- post the public resolution back to GitHub\n- mark the Linear task accordingly\n\n## Review Rules\n\n- Never merge from title, summary, or trust alone; use the full diff\n- External-source features should be rebuilt inside ECC when they are valuable but not self-contained\n- CI red means classify and fix or block; do not pretend it is merge-ready\n- If the real blocker is product direction, say so instead of hiding behind tooling\n\n## Output Format\n\nReturn:\n\n```text\nPUBLIC STATUS\n- issue \u002F PR state\n- CI \u002F review state\n\nCLASSIFICATION\n- merge \u002F port-rebuild \u002F close \u002F park\n- one-paragraph rationale\n\nLINEAR ACTION\n- create \u002F update \u002F no Linear item needed\n- project \u002F lane if applicable\n\nNEXT OPERATOR ACTION\n- exact next move\n```\n\n## Good Use Cases\n\n- \"Audit the open PR backlog and tell me what to merge vs rebuild\"\n- \"Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes\"\n- \"Check whether this needs a Linear issue or should stay GitHub-only\"\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","everything-claude-code\u002Fskills\u002Fproject-flow-ops",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill project-flow-ops",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill project-flow-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill project-flow-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fskills\u002Fproject-flow-ops\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"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":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\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":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]