[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GQH36GWSSMXJ4B18TN3V7":3,"skill-same:01M70GQH36GWSSMXJ4B18TN3V7":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},"01M70GQH36GWSSMXJ4B18TN3V7","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.","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\u002Fproject-flow-ops\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"project flow ops","flow","project","ops","when","pull requests","linking","layer","operate","across","active","backlog","work","coordination","execution","pr triage","pull","linear","issues","pr","2026-11-10 10:12:30",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.\nmetadata:\n  origin: 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,"metadata":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fproject-flow-ops",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 project-flow-ops",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill project-flow-ops",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill project-flow-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fproject-flow-ops\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",[],[]]