yogsoth-ai/de-anthropocentric-research-engine

assess-removability

Estimate whether and at what cost a constraint can be removed or relaxed.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill assess-removability

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

assess-removability

Purpose

Estimate whether a constraint can be removed or relaxed, at what cost, and with which residual risks.

Input contract

yaml
required: [constraint_record, dependency_map, removal_options, cost_model]
optional: [time_horizon, safety_limits, stakeholder_requirements]
constraints: [each option states feasibility, cost units, dependencies, and residual risk]

Procedure

  1. Trace the constraint to dependent claims, processes, and safety conditions.
  2. Generate removal or relaxation options and estimate direct cost, delay, dependency changes, and residual risk.
  3. Test each option against non-negotiable boundaries and identify the cheapest feasible relaxation.
  4. Emit removability class, cost/risk profile, and a reversible trial where one exists.

Output contract

yaml
produces: [removability_assessment, option_comparison, residual_risks, recommended_trial]
delta_fields: [findings, evidence_updates, uncertainties, decisions, recommended_jumps]

Quality gates

  • A-class gate: declared universe = all identified constraints and removal options; numerator = options with dependency, cost, and residual-risk evidence; batch increment = one option assessed; stopping reason = all options assessed or a feasible dominant option is established; source references = dependency, cost, and risk IDs; direction/threshold reason = removability improves only when dependency burden and residual risk decrease without violating hard boundaries.
  • A removal claim must include at least one dependency, one cost, and one residual risk.

Failure and counterexamples

Do not label a constraint removable because it is inconvenient. If removal changes the target construct, report a scope change instead.

Provenance map

  • resolved: removability-assessment

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills