All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Product Ops Platform Closeout Handoff LedgerUse when a product platform and API operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the compatibility decision record with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Product Ops Platform Completeness ReconciliationUse when the product platform and API operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the compatibility decision record with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Product Ops Platform Exception Triage QueueUse when the product platform and API operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the compatibility decision record with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Product Ops Platform Recovery Readiness DrillUse when the product platform and API operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the compatibility decision record with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Product Ops Platform Scenario Sensitivity MatrixUse when the product platform and API operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the compatibility decision record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Product Ops Platform Scope Intake GateUse when a new product platform and API operations request needs a bounded work scope to produce a scoped intake card for the compatibility decision record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Product Ops Platform Source Provenance LedgerUse when a decision about product platform and API operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the compatibility decision record. Success means each material claim has a source, version/date, location, and confidence note; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Product Ops Platform Threshold Rule CheckUse when a product platform and API operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the compatibility decision record showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Product Ops Pricing Approval Evidence PacketUse when a pricing and packaging analysis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the pricing assumption matrix containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Product Ops Pricing Change Impact TraceUse when a version, rule, source, or stakeholder change may affect pricing and packaging analysis to produce a before/after change record and impact map for the pricing assumption matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Product Ops Pricing Closeout Handoff LedgerUse when a pricing and packaging analysis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the pricing assumption matrix with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Product Ops Pricing Completeness ReconciliationUse when the pricing and packaging analysis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the pricing assumption matrix with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Product Ops Pricing Exception Triage QueueUse when the pricing and packaging analysis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the pricing assumption matrix with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Product Ops Pricing Recovery Readiness DrillUse when the pricing and packaging analysis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the pricing assumption matrix with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Product Ops Pricing Scenario Sensitivity MatrixUse when the pricing and packaging analysis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the pricing assumption matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Product Ops Pricing Scope Intake GateUse when a new pricing and packaging analysis request needs a bounded work scope to produce a scoped intake card for the pricing assumption matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused p...Votes: 0GitHub stars: 2
- Product Ops Pricing Source Provenance LedgerUse when a decision about pricing and packaging analysis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the pricing assumption matrix. Success means each material claim has a source, version/date, location, and confidence note; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit r...Votes: 0GitHub stars: 2
- Product Ops Pricing Threshold Rule CheckUse when a pricing and packaging analysis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the pricing assumption matrix showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; all price comparisons use a comparable unit and assumptions remain visible. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Product Ops Release Approval Evidence PacketUse when a product release readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the release readiness packet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Product Ops Release Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product release readiness to produce a before/after change record and impact map for the release readiness packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Product Ops Release Closeout Handoff LedgerUse when a product release readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the release readiness packet with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Product Ops Release Completeness ReconciliationUse when the product release readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the release readiness packet with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Product Ops Release Exception Triage QueueUse when the product release readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the release readiness packet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Product Ops Release Recovery Readiness DrillUse when the product release readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the release readiness packet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Product Ops Release Scenario Sensitivity MatrixUse when the product release readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the release readiness packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Product Ops Release Scope Intake GateUse when a new product release readiness request needs a bounded work scope to produce a scoped intake card for the release readiness packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and se...Votes: 0GitHub stars: 2
- Product Ops Release Source Provenance LedgerUse when a decision about product release readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the release readiness packet. Success means each material claim has a source, version/date, location, and confidence note; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Product Ops Release Threshold Rule CheckUse when a product release readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the release readiness packet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; every release gate has evidence, an owner, and a rollback condition. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Product Ops Requirements Approval Evidence PacketUse when a product requirements result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the requirements brief containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Product Ops Requirements Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product requirements to produce a before/after change record and impact map for the requirements brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Product Ops Requirements Closeout Handoff LedgerUse when a product requirements work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the requirements brief with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Product Ops Requirements Completeness ReconciliationUse when the product requirements workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the requirements brief with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Product Ops Requirements Exception Triage QueueUse when the product requirements workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the requirements brief with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Product Ops Requirements Recovery Readiness DrillUse when the product requirements workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the requirements brief with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Product Ops Requirements Scenario Sensitivity MatrixUse when the product requirements team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the requirements brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Product Ops Requirements Scope Intake GateUse when a new product requirements request needs a bounded work scope to produce a scoped intake card for the requirements brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and se...Votes: 0GitHub stars: 2
- Product Ops Requirements Source Provenance LedgerUse when a decision about product requirements depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the requirements brief. Success means each material claim has a source, version/date, location, and confidence note; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Product Ops Requirements Threshold Rule CheckUse when a product requirements decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the requirements brief showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; every requirement has a testable outcome and no unapproved solution is implied. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Product Ops Roadmap Approval Evidence PacketUse when a roadmap portfolio result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the roadmap decision ledger containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Product Ops Roadmap Change Impact TraceUse when a version, rule, source, or stakeholder change may affect roadmap portfolio to produce a before/after change record and impact map for the roadmap decision ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authoriz...Votes: 0GitHub stars: 2
- Product Ops Roadmap Closeout Handoff LedgerUse when a roadmap portfolio work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the roadmap decision ledger with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Product Ops Roadmap Completeness ReconciliationUse when the roadmap portfolio workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the roadmap decision ledger with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Product Ops Roadmap Exception Triage QueueUse when the roadmap portfolio workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the roadmap decision ledger with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Product Ops Roadmap Recovery Readiness DrillUse when the roadmap portfolio workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the roadmap decision ledger with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Product Ops Roadmap Scenario Sensitivity MatrixUse when the roadmap portfolio team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the roadmap decision ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Product Ops Roadmap Scope Intake GateUse when a new roadmap portfolio request needs a bounded work scope to produce a scoped intake card for the roadmap decision ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes...Votes: 0GitHub stars: 2
- Product Ops Roadmap Source Provenance LedgerUse when a decision about roadmap portfolio depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the roadmap decision ledger. Success means each material claim has a source, version/date, location, and confidence note; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refine...Votes: 0GitHub stars: 2
- Product Ops Roadmap Threshold Rule CheckUse when a roadmap portfolio decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the roadmap decision ledger showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; priorities show trade-offs and no date is presented as a commitment without approval. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Product Ops Sunset Approval Evidence PacketUse when a feature sunset and migration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sunset readiness plan containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Product Ops Sunset Change Impact TraceUse when a version, rule, source, or stakeholder change may affect feature sunset and migration to produce a before/after change record and impact map for the sunset readiness plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Re...Votes: 0GitHub stars: 2