All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Agent Coordination Artifact Integration Approval Evidence PacketUse when a parallel artifact integration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the integration staging 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; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Change Impact TraceUse when a version, rule, source, or stakeholder change may affect parallel artifact integration to produce a before/after change record and impact map for the integration staging plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Closeout Handoff LedgerUse when a parallel artifact integration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the integration staging plan 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; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Completeness ReconciliationUse when the parallel artifact integration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the integration staging plan 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; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Exception Triage QueueUse when the parallel artifact integration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the integration staging plan 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; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Recovery Readiness DrillUse when the parallel artifact integration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the integration staging plan 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; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Scenario Sensitivity MatrixUse when the parallel artifact integration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the integration staging plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Scope Intake GateUse when a new parallel artifact integration request needs a bounded work scope to produce a scoped intake card for the integration staging plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Source Provenance LedgerUse when a decision about parallel artifact integration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the integration staging plan. Success means each material claim has a source, version/date, location, and confidence note; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Aas Agent Coordination Artifact Integration Threshold Rule CheckUse when a parallel artifact integration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the integration staging plan 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; each output is reviewed against the same baseline and conflicts remain visible. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Approval Evidence PacketUse when a delegated task cancellation propagation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured searc...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect delegated task cancellation propagation to produce a before/after change record and impact map for the cancellation propagation check. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Closeout Handoff LedgerUse when a delegated task cancellation propagation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Completeness ReconciliationUse when the delegated task cancellation propagation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Exception Triage QueueUse when the delegated task cancellation propagation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Recovery Readiness DrillUse when the delegated task cancellation propagation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Scenario Sensitivity MatrixUse when the delegated task cancellation propagation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the cancellation propagation check with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Scope Intake GateUse when a new delegated task cancellation propagation request needs a bounded work scope to produce a scoped intake card for the cancellation propagation check. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Source Provenance LedgerUse when a decision about delegated task cancellation propagation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the cancellation propagation check. Success means each material claim has a source, version/date, location, and confidence note; all cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authori...Votes: 0GitHub stars: 2
- Aas Agent Coordination Cancel Propagation Threshold Rule CheckUse when a delegated task cancellation propagation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. Use configured search, ...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Approval Evidence PacketUse when a multi-agent checkpoint and resume result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Change Impact TraceUse when a version, rule, source, or stakeholder change may affect multi-agent checkpoint and resume to produce a before/after change record and impact map for the resume checkpoint manifest. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Closeout Handoff LedgerUse when a multi-agent checkpoint and resume work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Completeness ReconciliationUse when the multi-agent checkpoint and resume workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Exception Triage QueueUse when the multi-agent checkpoint and resume workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Recovery Readiness DrillUse when the multi-agent checkpoint and resume workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Scenario Sensitivity MatrixUse when the multi-agent checkpoint and resume team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the resume checkpoint manifest with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Scope Intake GateUse when a new multi-agent checkpoint and resume request needs a bounded work scope to produce a scoped intake card for the resume checkpoint manifest. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three f...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Source Provenance LedgerUse when a decision about multi-agent checkpoint and resume depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the resume checkpoint manifest. Success means each material claim has a source, version/date, location, and confidence note; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Checkpoint Resume Threshold Rule CheckUse when a multi-agent checkpoint and resume decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Approval Evidence PacketUse when a delegated context handoff result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Change Impact TraceUse when a version, rule, source, or stakeholder change may affect delegated context handoff to produce a before/after change record and impact map for the minimal context handoff packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Closeout Handoff LedgerUse when a delegated context handoff work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Completeness ReconciliationUse when the delegated context handoff workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Exception Triage QueueUse when the delegated context handoff workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Recovery Readiness DrillUse when the delegated context handoff workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Scenario Sensitivity MatrixUse when the delegated context handoff team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the minimal context handoff packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Scope Intake GateUse when a new delegated context handoff request needs a bounded work scope to produce a scoped intake card for the minimal context handoff packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three foc...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Source Provenance LedgerUse when a decision about delegated context handoff depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the minimal context handoff packet. Success means each material claim has a source, version/date, location, and confidence note; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2
- Aas Agent Coordination Context Handoff Threshold Rule CheckUse when a delegated context handoff decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Approval Evidence PacketUse when a agent task dependency graphs result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent task dependency graphs to produce a before/after change record and impact map for the task dependency graph. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and autho...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Closeout Handoff LedgerUse when a agent task dependency graphs work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Completeness ReconciliationUse when the agent task dependency graphs workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Exception Triage QueueUse when the agent task dependency graphs workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Recovery Readiness DrillUse when the agent task dependency graphs workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Scenario Sensitivity MatrixUse when the agent task dependency graphs team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the task dependency graph with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Scope Intake GateUse when a new agent task dependency graphs request needs a bounded work scope to produce a scoped intake card for the task dependency graph. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused pas...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Source Provenance LedgerUse when a decision about agent task dependency graphs depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the task dependency graph. Success means each material claim has a source, version/date, location, and confidence note; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ref...Votes: 0GitHub stars: 2
- Aas Agent Coordination Dependency Graph Threshold Rule CheckUse when a agent task dependency graphs decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2