/analyze-constraints-readiness

name: analyze-constraints-readiness
description: "Characterize what blocks a research target: readiness dimensions, obstacles, bottlenecks, resource gaps, causal constraints, dependencies, conflicts, removability, and mitigation pathways. Depth selects lightweight triage, readiness assessment, or causal/TOC-style constraint analysis."

analyze-constraints-readiness

Purpose

Assess feasibility and readiness by identifying constraints, resources, dependencies, bottlenecks, and maturation gates.

Input contract

mode_contracts:
  obstacle-triage: &readiness_input
    required: [candidate_or_plan, readiness_dimensions]
    optional: [resource_estimates, dependencies, assumptions, target_gates]
    constraints: [evidence_must_be_attached_to_each_scored_dimension]
  readiness-assessment: *readiness_input
  resource-envelope: *readiness_input
  causal-constraint-analysis: *readiness_input
  maturation-path: *readiness_input

Execution protocol

Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.

1. Define candidate, dimensions, hard constraints, and target gates. You MUST load skill `classify-constraint` to classify each declared constraint. 2. Select `obstacle-triage`, `readiness-assessment`, `resource-envelope`, `causal-constraint-analysis`, or `maturation-path`. 3. You MUST load skill `score-object` to score the selected dimensions with evidence. You MUST load skill `identify-bottleneck` to identify binding constraints and dependencies. 4. You MUST load skill `assess-removability` to test whether binding constraints can be removed. You MUST load skill `design-mitigation` to design removal or mitigation paths and return a readiness conclusion. If several feasible responses must be balanced as a joint set, consider `portfolio-optimization`. If the target goal remains too broad to assess, consider `decompose-research-goal`. If external change dominates present readiness, consider `analyze-future-scenarios`. If several candidate paths are ready for comparative selection, `rank-candidates` may be the better next tactic.

Mode branches

• `obstacle-triage`: rapidly enumerate and severity-rank the obstacles that could block the target, preserving evidence status for each one. You MUST load skill `identify-obstacles` to enumerate the obstacles. You MUST load skill `list-undesirable-effects` to retain their observed consequences.
• `readiness-assessment`: score the required readiness dimensions with supporting evidence and identify the dimensions that keep the target from being ready. You MUST load skill `assess-readiness-dimension` to assess every required dimension.
• `resource-envelope`: estimate time, cost, and personnel bounds from analogies, then flag low-confidence estimates for investigation. You MUST load skill `quantify-resource-gap` to quantify the gap. You MUST load skill `identify-critical-chain` to expose the binding resource sequence.
• `causal-constraint-analysis`: trace how constraints interact through dependencies and conflicts to identify the binding cause rather than only its symptoms. You MUST load skill `trace-causal-chain` to trace constraint propagation. You MUST load skill `extract-core-conflict` to isolate the core conflict. You MUST load skill `challenge-assumption` to test the assumptions that sustain it.
• `maturation-path`: sequence stage gates and milestones that move the target from current readiness to the declared implementation threshold. You MUST load skill `project-future-reality` to project the proposed path. You MUST load skill `apply-stage-gate` to apply its stage gates.

Output contract

mode_contracts:
  obstacle-triage: &constraint_output
    produces: [constraint_register, bottlenecks, mitigation_paths]
    delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
  readiness-assessment:
    produces: [readiness_profile, bottlenecks]
    delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
  resource-envelope:
    produces: [resource_envelope, bottlenecks, mitigation_paths]
    delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]
  causal-constraint-analysis: *constraint_output
  maturation-path:
    produces: [readiness_profile, resource_envelope, stage_gates, mitigation_paths]
    delta_fields: [findings, decisions, uncertainties, open_questions, recommended_jumps]

Thresholds and quality gates

• Feasibility, maturity, constraint, resource, and maturation gates use declared dimension/evidence/constraint coverage ratios; record numerator, denominator, batch increment, stopping reason, and source references.
• Preserve structural requirements: at least one hard constraint, one removal path per removable constraint, explicit stage gates, and a binding-constraint rule relative to the observed score distribution.

• Feasibility dimensions >=5; blockers >=3 per candidate where source protocol applies.
• Maturity diagnosis: >=5 dimensions, >=2 evidence items per dimension, >=1 bottleneck.
• Constraint identification: >=3 constraints per candidate; >=1 hard constraint; >=1 removal path per removable constraint.
• Resource envelope: >=3 dimensions (time, cost, personnel) and >=2 analogies per estimate.
• Maturation path: >=3 stage gates and >=2 milestones per stage.
• Binding constraint threshold: sensitivity score >2* median.

Failure and counterexamples

Do not label a candidate ready with missing evidence, unclassified hard constraints, or an unbounded resource estimate. A conflict with no manageable injection remains blocked.

Provenance map

26 architecture `old` entries; readiness, feasibility, resource, obstacle, dependency, sensitivity, and maturation families are merged by mode. Missing aliases are listed in log.

Legacy context checkpoint / Delta notes

Append dimension scores/evidence, constraint IDs, bottleneck rationale, resources, gates, and unresolv