[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF2QZEWCM78V1F0VM4PRWT":3,"skill-same:01M7AF2QZEWCM78V1F0VM4PRWT":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AF2QZEWCM78V1F0VM4PRWT","sprint-planning-skill",null,"Plan sprints by scoping work, estimating capacity, setting goals, and mapping dependencies. Use when kicking off a new sprint, rebalancing mid-sprint, or reviewing capacity for upcoming work. Trigger with \"plan next sprint\", \"sprint planning for\", \"what fits in this sprint\".","innFactory-AI\u002Fcompany-ai-stack-skills","innFactory-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165681221?v=4","01M7AEC27VD0D1QX2XBX441MDW","innFactory AI","01M7AEC28G25HQ9H9SN58MNV27",0,"MIT","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproduct-management\u002Fsprint-planning-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sprint-planning-skill\ndescription: Plan sprints by scoping work, estimating capacity, setting goals, and mapping dependencies. Use when kicking off a new sprint, rebalancing mid-sprint, or reviewing capacity for upcoming work. Trigger with \"plan next sprint\", \"sprint planning for\", \"what fits in this sprint\".\n---\n\n# Sprint Planning Skill\n\nPlan fixed-length iteration cycles — scope work to capacity, set outcome-oriented sprint goals, map dependencies, and distinguish commitments from stretch items. Team metrics and backlog data come from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **Project tracker via MCP** (e.g. Jira, Linear, GitHub) | Backlog items, story estimates, historical velocity, sprint status, ownership |\n| **companyRAG collections** | Roadmap, OKRs, technical specs, team agreements, retrospective notes |\n| **File upload** | Capacity spreadsheets, velocity history, exported backlog lists |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Capacity Estimation\n\n### Step 1: Calculate Raw Capacity\n\nRaw capacity is the theoretical maximum before adjustments.\n\n```\nRAW CAPACITY = Team members × Sprint length (days) × Hours per day\n```\n\nUse the team's standard working hours — do NOT assume 8 hours\u002Fday of productive engineering time. Most teams operate at 5–6 productive hours\u002Fday after meetings, context switching, and overhead.\n\n### Step 2: Apply Availability Adjustments\n\nReduce raw capacity for known absences:\n\n| Adjustment | How to Apply |\n| --- | --- |\n| **PTO \u002F holidays** | Subtract full days per person |\n| **On-call rotation** | Reduce that person's capacity by 30–50% (based on historical interrupt rate) |\n| **Recurring meetings** | Subtract total meeting hours across the sprint per person |\n| **Onboarding \u002F ramp-up** | New team members at 25–50% capacity for first 2–4 sprints |\n| **Support rotation** | Subtract the team's historical average for support work |\n\n```\nADJUSTED CAPACITY = RAW CAPACITY − (PTO hours + on-call reduction + meetings + support)\n```\n\n### Step 3: Apply Focus Factor\n\nThe focus factor accounts for unplanned work, bug fixes, code review, and other overhead not captured above. Derive it from the team's own history:\n\n```\nFOCUS FACTOR = (Actual story points completed) \u002F (Adjusted capacity in hours) — averaged over last 3–5 sprints\n```\n\nIf historical data is unavailable, start with 0.7 (70%) and calibrate after 2–3 sprints. Never prescribe a universal focus factor — it varies by team maturity, codebase health, and interrupt patterns.\n\n```\nEFFECTIVE CAPACITY = ADJUSTED CAPACITY × FOCUS FACTOR\n```\n\n### Step 4: Express as Story Points or Hours\n\nConvert effective capacity into the team's estimation unit. If the team uses story points, map via historical velocity:\n\n```\nSPRINT CAPACITY (points) = Average velocity over last 3–5 sprints, adjusted for capacity differences\n```\n\nIf this sprint has 80% of normal capacity, plan for roughly 80% of average velocity. Velocity is an empirical measure, not a target — do not inflate or \"stretch\" it.\n\n## Sprint Goal Definition\n\nA sprint goal is an outcome statement, not a list of tickets. It answers: \"If we complete this sprint successfully, what will be true that isn't true today?\"\n\n### Goal Quality Checklist\n\n| Criterion | Pass | Fail |\n| --- | --- | --- |\n| **Outcome-oriented** | \"Users can complete checkout without page refresh\" | \"Finish tickets ENG-123, ENG-124, ENG-125\" |\n| **Singular focus** | One coherent theme or objective | Multiple unrelated objectives bundled |\n| **Testable** | A demo or metric can verify achievement | No way to know if the goal is met |\n| **Achievable** | Fits within sprint capacity after estimation | Requires optimistic assumptions about capacity |\n| **Stakeholder-meaningful** | Non-engineers can understand the value delivered | Expressed in purely technical jargon |\n\n### Goal Setting Process\n\n1. Review product priorities: What is the highest-impact work from the backlog? Reference the roadmap and current OKRs.\n2. Draft 1–2 candidate goals: Frame as outcomes, not task lists.\n3. Scope-check: Can the team realistically achieve this goal within effective capacity? If not, narrow scope — reduce the goal, don't reduce quality.\n4. Team alignment: The team must understand and commit to the goal. A goal imposed without team buy-in produces compliance, not commitment.\n\n## Dependency Mapping\n\n### Dependency Categories\n\n| Type | Definition | Mitigation |\n| --- | --- | --- |\n| **Internal team** | Work that depends on another story within the same sprint | Sequence stories; pair-assign if possible |\n| **Cross-team** | Work blocked by another team's deliverable | Confirm delivery date before sprint commitment; add buffer |\n| **External** | Third-party API, vendor deliverable, customer approval | Do not commit dependent work without confirmed timeline |\n| **Technical** | Shared infrastructure, database migration, deployment pipeline | Identify and schedule early in the sprint |\n\n### Dependency Resolution Protocol\n\nFor each dependency identified:\n\n1. Classify by type (above)\n2. Confirm status: Is the dependency already resolved, in progress, or not started?\n3. Assess risk: What happens if the dependency is late? Is there alternative work the team can pull?\n4. Assign owner: Someone on the team owns tracking each external dependency\n5. Set check-in: When will you verify the dependency is on track? (Not the last day of the sprint)\n\n**Rule**: If a story has an unresolved external dependency with no confirmed delivery date, it goes to stretch — never commitment.\n\n## Commitment vs. Stretch\n\nSplit the sprint backlog into two explicit categories:\n\n### Commitment\n\nWork the team is confident they will complete within the sprint. Confidence threshold: the team believes there is at least an 80–90% chance of completion given effective capacity.\n\n- Must fit within effective capacity\n- Dependencies must be resolved or have confirmed delivery dates\n- Acceptance criteria must be clear — if the team cannot describe \"done,\" it is not ready for commitment\n\n### Stretch\n\nWork the team will pull if commitment items finish early. Stretch items:\n\n- Are fully groomed and ready to start (no blocking questions)\n- Have no unresolved dependencies\n- Are independent — pulling a stretch item does not destabilise committed work\n- Are ordered by priority so the team knows what to pull first\n\n**Capacity allocation guideline**: Commit to 80–90% of effective capacity; fill the remaining 10–20% with ordered stretch items. The exact ratio depends on the team's historical accuracy — teams that consistently under-commit can tighten the ratio; teams that over-commit should loosen it.\n\n## Sprint Planning Workflow\n\n### Before Planning (Preparation)\n\n1. Groom the backlog: Top candidates must have clear descriptions, acceptance criteria, and estimates. Ungroomed items cannot enter the sprint.\n2. Calculate capacity: Run Steps 1–4 from Capacity Estimation with current sprint data.\n3. Surface dependencies: Identify cross-team and external dependencies for candidate stories.\n4. Review prior sprint: What carried over? What was learned? Carry-over items get priority consideration but are not automatically included — reassess priority.\n\n### During Planning\n\n1. Present the sprint goal (from Goal Definition above)\n2. Walk the candidate stories: For each, confirm scope, estimate, dependencies, and acceptance criteria\n3. Load commitment: Add stories to commitment until effective capacity is reached\n4. Sequence for dependencies: Order committed stories so that dependent work starts after its prerequisites\n5. Add stretch: Fill the stretch backlog in priority order\n6. Team confirmation: Each team member confirms they understand their work and believe the commitment is achievable\n\n### Sprint Plan Output\n\n```\nSPRINT: [Name \u002F Number]\nDATES:  [Start] — [End]\nGOAL:   [Outcome statement]\n\nCAPACITY:\n  Team members:       [count]\n  Raw capacity:       [hours or points]\n  Adjustments:        [PTO, on-call, etc.]\n  Effective capacity: [final number]\n  Velocity reference: [last 3–5 sprint average]\n\nCOMMITMENT: [total points\u002Fhours] ([X]% of effective capacity)\n  | # | Story | Estimate | Owner | Dependencies | Status |\n  |---|-------|----------|-------|--------------|--------|\n  | 1 | [title] | [est] | [name] | [deps] | Ready |\n\nSTRETCH: [total points\u002Fhours]\n  | # | Story | Estimate | Pull Priority | Dependencies |\n  |---|-------|----------|---------------|--------------|\n  | 1 | [title] | [est] | 1 (pull first) | [deps] |\n\nDEPENDENCIES:\n  | Dependency | Type | Owner | Expected Resolution | Check-in Date |\n  |------------|------|-------|---------------------|---------------|\n\nRISKS:\n  [Key risks to sprint goal achievement — from dependency analysis and capacity review]\n\nCARRY-OVER FROM PREVIOUS SPRINT:\n  [Items, reason for carry-over, updated priority assessment]\n```\n\n## Mid-Sprint Rebalancing\n\nWhen sprint health deteriorates (blocked items, scope changes, unexpected absences), use this triage:\n\n1. Assess remaining capacity: Recalculate effective capacity for the remaining sprint days\n2. Re-evaluate commitment: Which committed items are at risk? Which are on track?\n3. Protect the sprint goal: If the goal is achievable with a subset of committed work, shed non-goal items to stretch\n4. Escalate blockers: Unresolved dependencies that threaten the sprint goal require immediate escalation — do not wait for the next stand-up\n5. Communicate: If the commitment changes, inform stakeholders — use the write-stakeholder-update skill\n\n## Guardrails\n\n- NEVER generate velocity data, estimates, or capacity numbers. All team metrics must come from the user, project tracker, or a companyRAG collection.\n- NEVER prescribe universal focus factors, velocity targets, or capacity ratios. Teach the calculation; the team derives their own numbers.\n- NEVER populate sprint plans with fabricated stories or estimates. Generate blank templates when no data is provided.\n- Source-label every element as `[From user\u002Ftracker data]`, `[From sprint planning framework]`, or `[AI suggestion — verify with team]`.\n\n> **Tip:** Ask for Markdown, DOCX, or XLSX output via companyFILES to get a formatted sprint plan ready to share.\n","# Sprint Planning Skill\n\nPlan fixed-length iteration cycles — scope work to capacity, set outcome-oriented sprint goals, map dependencies, and distinguish commitments from stretch items. Team metrics and backlog data come from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **Project tracker via MCP** (e.g. Jira, Linear, GitHub) | Backlog items, story estimates, historical velocity, sprint status, ownership |\n| **companyRAG collections** | Roadmap, OKRs, technical specs, team agreements, retrospective notes |\n| **File upload** | Capacity spreadsheets, velocity history, exported backlog lists |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Capacity Estimation\n\n### Step 1: Calculate Raw Capacity\n\nRaw capacity is the theoretical maximum before adjustments.\n\n```\nRAW CAPACITY = Team members × Sprint length (days) × Hours per day\n```\n\nUse the team's standard working hours — do NOT assume 8 hours\u002Fday of productive engineering time. Most teams operate at 5–6 productive hours\u002Fday after meetings, context switching, and overhead.\n\n### Step 2: Apply Availability Adjustments\n\nReduce raw capacity for known absences:\n\n| Adjustment | How to Apply |\n| --- | --- |\n| **PTO \u002F holidays** | Subtract full days per person |\n| **On-call rotation** | Reduce that person's capacity by 30–50% (based on historical interrupt rate) |\n| **Recurring meetings** | Subtract total meeting hours across the sprint per person |\n| **Onboarding \u002F ramp-up** | New team members at 25–50% capacity for first 2–4 sprints |\n| **Support rotation** | Subtract the team's historical average for support work |\n\n```\nADJUSTED CAPACITY = RAW CAPACITY − (PTO hours + on-call reduction + meetings + support)\n```\n\n### Step 3: Apply Focus Factor\n\nThe focus factor accounts for unplanned work, bug fixes, code review, and other overhead not captured above. Derive it from the team's own history:\n\n```\nFOCUS FACTOR = (Actual story points completed) \u002F (Adjusted capacity in hours) — averaged over last 3–5 sprints\n```\n\nIf historical data is unavailable, start with 0.7 (70%) and calibrate after 2–3 sprints. Never prescribe a universal focus factor — it varies by team maturity, codebase health, and interrupt patterns.\n\n```\nEFFECTIVE CAPACITY = ADJUSTED CAPACITY × FOCUS FACTOR\n```\n\n### Step 4: Express as Story Points or Hours\n\nConvert effective capacity into the team's estimation unit. If the team uses story points, map via historical velocity:\n\n```\nSPRINT CAPACITY (points) = Average velocity over last 3–5 sprints, adjusted for capacity differences\n```\n\nIf this sprint has 80% of normal capacity, plan for roughly 80% of average velocity. Velocity is an empirical measure, not a target — do not inflate or \"stretch\" it.\n\n## Sprint Goal Definition\n\nA sprint goal is an outcome statement, not a list of tickets. It answers: \"If we complete this sprint successfully, what will be true that isn't true today?\"\n\n### Goal Quality Checklist\n\n| Criterion | Pass | Fail |\n| --- | --- | --- |\n| **Outcome-oriented** | \"Users can complete checkout without page refresh\" | \"Finish tickets ENG-123, ENG-124, ENG-125\" |\n| **Singular focus** | One coherent theme or objective | Multiple unrelated objectives bundled |\n| **Testable** | A demo or metric can verify achievement | No way to know if the goal is met |\n| **Achievable** | Fits within sprint capacity after estimation | Requires optimistic assumptions about capacity |\n| **Stakeholder-meaningful** | Non-engineers can understand the value delivered | Expressed in purely technical jargon |\n\n### Goal Setting Process\n\n1. Review product priorities: What is the highest-impact work from the backlog? Reference the roadmap and current OKRs.\n2. Draft 1–2 candidate goals: Frame as outcomes, not task lists.\n3. Scope-check: Can the team realistically achieve this goal within effective capacity? If not, narrow scope — reduce the goal, don't reduce quality.\n4. Team alignment: The team must understand and commit to the goal. A goal imposed without team buy-in produces compliance, not commitment.\n\n## Dependency Mapping\n\n### Dependency Categories\n\n| Type | Definition | Mitigation |\n| --- | --- | --- |\n| **Internal team** | Work that depends on another story within the same sprint | Sequence stories; pair-assign if possible |\n| **Cross-team** | Work blocked by another team's deliverable | Confirm delivery date before sprint commitment; add buffer |\n| **External** | Third-party API, vendor deliverable, customer approval | Do not commit dependent work without confirmed timeline |\n| **Technical** | Shared infrastructure, database migration, deployment pipeline | Identify and schedule early in the sprint |\n\n### Dependency Resolution Protocol\n\nFor each dependency identified:\n\n1. Classify by type (above)\n2. Confirm status: Is the dependency already resolved, in progress, or not started?\n3. Assess risk: What happens if the dependency is late? Is there alternative work the team can pull?\n4. Assign owner: Someone on the team owns tracking each external dependency\n5. Set check-in: When will you verify the dependency is on track? (Not the last day of the sprint)\n\n**Rule**: If a story has an unresolved external dependency with no confirmed delivery date, it goes to stretch — never commitment.\n\n## Commitment vs. Stretch\n\nSplit the sprint backlog into two explicit categories:\n\n### Commitment\n\nWork the team is confident they will complete within the sprint. Confidence threshold: the team believes there is at least an 80–90% chance of completion given effective capacity.\n\n- Must fit within effective capacity\n- Dependencies must be resolved or have confirmed delivery dates\n- Acceptance criteria must be clear — if the team cannot describe \"done,\" it is not ready for commitment\n\n### Stretch\n\nWork the team will pull if commitment items finish early. Stretch items:\n\n- Are fully groomed and ready to start (no blocking questions)\n- Have no unresolved dependencies\n- Are independent — pulling a stretch item does not destabilise committed work\n- Are ordered by priority so the team knows what to pull first\n\n**Capacity allocation guideline**: Commit to 80–90% of effective capacity; fill the remaining 10–20% with ordered stretch items. The exact ratio depends on the team's historical accuracy — teams that consistently under-commit can tighten the ratio; teams that over-commit should loosen it.\n\n## Sprint Planning Workflow\n\n### Before Planning (Preparation)\n\n1. Groom the backlog: Top candidates must have clear descriptions, acceptance criteria, and estimates. Ungroomed items cannot enter the sprint.\n2. Calculate capacity: Run Steps 1–4 from Capacity Estimation with current sprint data.\n3. Surface dependencies: Identify cross-team and external dependencies for candidate stories.\n4. Review prior sprint: What carried over? What was learned? Carry-over items get priority consideration but are not automatically included — reassess priority.\n\n### During Planning\n\n1. Present the sprint goal (from Goal Definition above)\n2. Walk the candidate stories: For each, confirm scope, estimate, dependencies, and acceptance criteria\n3. Load commitment: Add stories to commitment until effective capacity is reached\n4. Sequence for dependencies: Order committed stories so that dependent work starts after its prerequisites\n5. Add stretch: Fill the stretch backlog in priority order\n6. Team confirmation: Each team member confirms they understand their work and believe the commitment is achievable\n\n### Sprint Plan Output\n\n```\nSPRINT: [Name \u002F Number]\nDATES:  [Start] — [End]\nGOAL:   [Outcome statement]\n\nCAPACITY:\n  Team members:       [count]\n  Raw capacity:       [hours or points]\n  Adjustments:        [PTO, on-call, etc.]\n  Effective capacity: [final number]\n  Velocity reference: [last 3–5 sprint average]\n\nCOMMITMENT: [total points\u002Fhours] ([X]% of effective capacity)\n  | # | Story | Estimate | Owner | Dependencies | Status |\n  |---|-------|----------|-------|--------------|--------|\n  | 1 | [title] | [est] | [name] | [deps] | Ready |\n\nSTRETCH: [total points\u002Fhours]\n  | # | Story | Estimate | Pull Priority | Dependencies |\n  |---|-------|----------|---------------|--------------|\n  | 1 | [title] | [est] | 1 (pull first) | [deps] |\n\nDEPENDENCIES:\n  | Dependency | Type | Owner | Expected Resolution | Check-in Date |\n  |------------|------|-------|---------------------|---------------|\n\nRISKS:\n  [Key risks to sprint goal achievement — from dependency analysis and capacity review]\n\nCARRY-OVER FROM PREVIOUS SPRINT:\n  [Items, reason for carry-over, updated priority assessment]\n```\n\n## Mid-Sprint Rebalancing\n\nWhen sprint health deteriorates (blocked items, scope changes, unexpected absences), use this triage:\n\n1. Assess remaining capacity: Recalculate effective capacity for the remaining sprint days\n2. Re-evaluate commitment: Which committed items are at risk? Which are on track?\n3. Protect the sprint goal: If the goal is achievable with a subset of committed work, shed non-goal items to stretch\n4. Escalate blockers: Unresolved dependencies that threaten the sprint goal require immediate escalation — do not wait for the next stand-up\n5. Communicate: If the commitment changes, inform stakeholders — use the write-stakeholder-update skill\n\n## Guardrails\n\n- NEVER generate velocity data, estimates, or capacity numbers. All team metrics must come from the user, project tracker, or a companyRAG collection.\n- NEVER prescribe universal focus factors, velocity targets, or capacity ratios. Teach the calculation; the team derives their own numbers.\n- NEVER populate sprint plans with fabricated stories or estimates. Generate blank templates when no data is provided.\n- Source-label every element as `[From user\u002Ftracker data]`, `[From sprint planning framework]`, or `[AI suggestion — verify with team]`.\n\n> **Tip:** Ask for Markdown, DOCX, or XLSX output via companyFILES to get a formatted sprint plan ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fproduct-management\u002Fsprint-planning-skill","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills","https:\u002F\u002Fgithub.com\u002FinnFactory-AI","https:\u002F\u002Finnfactory.ai","Engineering AI. Enabling Tomorrow.","2026-11-13 19:54:47",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill sprint-planning-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill sprint-planning-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill sprint-planning-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproduct-management\u002Fsprint-planning-skill\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AF4HHK5B987T44HW7BZFVZ","sales-asset-skill","Produce tailored one-pagers, landing pages, case study drafts, and demo narratives personalised to a specific deal and buyer persona. Use when preparing collateral for a specific deal, building leave-behind materials, or customising standard assets for a prospect. Trigger with \"create a one-pager for\", \"sales deck for [deal]\", \"customise this asset for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fsales-asset-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"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},"01M7AF4D32V0FJE0QGCBZSQ7BW","pipeline-review-skill","Analyse deal health, surface stale or at-risk opportunities, and produce a prioritised weekly action plan. Use when preparing for a pipeline review meeting, assessing forecast accuracy, or identifying stuck deals. Trigger with \"review my pipeline\", \"pipeline health check\", \"deal risk analysis\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fpipeline-review-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AF48W7G8DMAHRAM125B192","outreach-skill","Research a prospect then draft personalised outreach with research-backed hooks, subject-line variants, and follow-up sequences. Use when cold-emailing a prospect, writing LinkedIn outreach, or building a multi-touch sequence. Trigger with \"draft outreach to [person\u002Fcompany]\", \"write cold email to\", \"outreach sequence for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Foutreach-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AF43VKNPQ7G1NTQ4MRH40J","forecast-skill","Build a weighted revenue forecast with risk flags, commit recommendations, and gap-to-quota analysis. Use when preparing for a forecast call, evaluating end-of-quarter projections, or assessing pipeline coverage. Trigger with \"build forecast\", \"forecast for this quarter\", \"where do I stand against quota\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fforecast-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AF3Z5N61VYSEJRYWXR4JP1","deal-strategy-skill","Map stakeholder power dynamics, surface deal risks, and recommend a step-by-step engagement strategy. Use when entering a complex deal, preparing for an executive sponsor meeting, or diagnosing a stuck opportunity. Trigger with \"plan deal strategy for\", \"stakeholder map\", \"how do I advance this deal\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fdeal-strategy-skill\u002FSKILL.md",[],[],{"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":19},"01M7AF3VGG29AX0T2X9WQ5MWDN","call-summary-skill","Extract action items, key topics, and objections from call notes or transcripts and draft a customer-facing follow-up email. Use after a sales call, demo, or discovery session. Trigger with \"summarise this call\", \"call notes from\", \"write follow-up for this meeting\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-summary-skill\u002FSKILL.md",[],[]]