All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Agri Ops Water Threshold Rule CheckUse when a farm water and irrigation planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the irrigation planning 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 water assumption is sourced and no control setting is changed automatically. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Built Env Change Orders Approval Evidence PacketUse when a change order and cost control result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the change impact 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; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Built Env Change Orders Change Impact TraceUse when a version, rule, source, or stakeholder change may affect change order and cost control to produce a before/after change record and impact map for the change impact ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Built Env Change Orders Closeout Handoff LedgerUse when a change order and cost control work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the change impact 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; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Built Env Change Orders Completeness ReconciliationUse when the change order and cost control workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the change impact 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; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Built Env Change Orders Exception Triage QueueUse when the change order and cost control workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the change impact 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; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Built Env Change Orders Recovery Readiness DrillUse when the change order and cost control workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the change impact 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; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Built Env Change Orders Scenario Sensitivity MatrixUse when the change order and cost control team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the change impact ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Built Env Change Orders Scope Intake GateUse when a new change order and cost control request needs a bounded work scope to produce a scoped intake card for the change impact ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three ...Votes: 0GitHub stars: 2
- Built Env Change Orders Source Provenance LedgerUse when a decision about change order and cost control depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the change impact ledger. Success means each material claim has a source, version/date, location, and confidence note; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence...Votes: 0GitHub stars: 2
- Built Env Change Orders Threshold Rule CheckUse when a change order and cost control decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the change impact 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; each delta is measured against the same baseline and remains uncommitted pending approval. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Built Env Commissioning Approval Evidence PacketUse when a handover and commissioning result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the commissioning evidence 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; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Built Env Commissioning Change Impact TraceUse when a version, rule, source, or stakeholder change may affect handover and commissioning to produce a before/after change record and impact map for the commissioning evidence matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Built Env Commissioning Closeout Handoff LedgerUse when a handover and commissioning work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the commissioning evidence 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; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Built Env Commissioning Completeness ReconciliationUse when the handover and commissioning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the commissioning evidence 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; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Built Env Commissioning Exception Triage QueueUse when the handover and commissioning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the commissioning evidence 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; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Built Env Commissioning Recovery Readiness DrillUse when the handover and commissioning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the commissioning evidence 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; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Built Env Commissioning Scenario Sensitivity MatrixUse when the handover and commissioning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the commissioning evidence matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Built Env Commissioning Scope Intake GateUse when a new handover and commissioning request needs a bounded work scope to produce a scoped intake card for the commissioning evidence matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each system has evidence, unresolved punch items, and named acceptance authority. 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
- Built Env Commissioning Source Provenance LedgerUse when a decision about handover and commissioning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the commissioning evidence matrix. Success means each material claim has a source, version/date, location, and confidence note; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2
- Built Env Commissioning Threshold Rule CheckUse when a handover and commissioning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the commissioning evidence 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; each system has evidence, unresolved punch items, and named acceptance authority. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Built Env Design Approval Evidence PacketUse when a design document coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the design coordination register 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 comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Built Env Design Change Impact TraceUse when a version, rule, source, or stakeholder change may affect design document coordination to produce a before/after change record and impact map for the design coordination register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Built Env Design Closeout Handoff LedgerUse when a design document coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the design coordination register 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 comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Built Env Design Completeness ReconciliationUse when the design document coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the design coordination register 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 comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Built Env Design Exception Triage QueueUse when the design document coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the design coordination register 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 comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Built Env Design Recovery Readiness DrillUse when the design document coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the design coordination register 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 comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Built Env Design Scenario Sensitivity MatrixUse when the design document coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the design coordination register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Built Env Design Scope Intake GateUse when a new design document coordination request needs a bounded work scope to produce a scoped intake card for the design coordination register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three fo...Votes: 0GitHub stars: 2
- Built Env Design Source Provenance LedgerUse when a decision about design document coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the design coordination register. Success means each material claim has a source, version/date, location, and confidence note; each comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Built Env Design Threshold Rule CheckUse when a design document coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the design coordination register 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 comment references the exact sheet/revision and has disposition or an owner. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Built Env Estimating Approval Evidence PacketUse when a estimating and bid review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the estimate basis worksheet 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 material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Built Env Estimating Change Impact TraceUse when a version, rule, source, or stakeholder change may affect estimating and bid review to produce a before/after change record and impact map for the estimate basis worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and auth...Votes: 0GitHub stars: 2
- Built Env Estimating Closeout Handoff LedgerUse when a estimating and bid review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the estimate basis worksheet 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 material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Built Env Estimating Completeness ReconciliationUse when the estimating and bid review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the estimate basis worksheet 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 material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Built Env Estimating Exception Triage QueueUse when the estimating and bid review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the estimate basis worksheet 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 material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Built Env Estimating Recovery Readiness DrillUse when the estimating and bid review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the estimate basis worksheet 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 material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Built Env Estimating Scenario Sensitivity MatrixUse when the estimating and bid review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the estimate basis worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Built Env Estimating Scope Intake GateUse when a new estimating and bid review request needs a bounded work scope to produce a scoped intake card for the estimate basis worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused pa...Votes: 0GitHub stars: 2
- Built Env Estimating Source Provenance LedgerUse when a decision about estimating and bid review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the estimate basis worksheet. Success means each material claim has a source, version/date, location, and confidence note; all material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Built Env Estimating Threshold Rule CheckUse when a estimating and bid review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the estimate basis worksheet 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 material quantities trace to a source and scope gaps are explicitly flagged. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Built Env Facilities Approval Evidence PacketUse when a facility operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the facility service review 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; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Built Env Facilities Change Impact TraceUse when a version, rule, source, or stakeholder change may affect facility operations to produce a before/after change record and impact map for the facility service review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and autho...Votes: 0GitHub stars: 2
- Built Env Facilities Closeout Handoff LedgerUse when a facility operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the facility service review 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; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Built Env Facilities Completeness ReconciliationUse when the facility operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the facility service review 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; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Built Env Facilities Exception Triage QueueUse when the facility operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the facility service review 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; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Built Env Facilities Recovery Readiness DrillUse when the facility operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the facility service review 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; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Built Env Facilities Scenario Sensitivity MatrixUse when the facility operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the facility service review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Built Env Facilities Scope Intake GateUse when a new facility operations request needs a bounded work scope to produce a scoped intake card for the facility service review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; work-order status and asset identity reconcile without changing live control settings. 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
- Built Env Facilities Source Provenance LedgerUse when a decision about facility operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the facility service review. Success means each material claim has a source, version/date, location, and confidence note; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ref...Votes: 0GitHub stars: 2