feasibility-assessment
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Feasibility Assessment Campaign — evaluate whether selected candidates can actually be implemented using TRL, NASSS, Stage-Gate, TRIZ, TOC, and parametric estimation methods.
In this repository119 other files it gives its agents.
- adaptive-pair-selectionSkill
- adversarial-debate-protocolSkill
- advocate-constructionSkill
- aggregation-methodSkill
- alternative-scoringSkill
- appropriateness-boundingSkill
- argument-crystallizationSkill
- argument-extractionSkill
- assumption-challengeSkill
- assumption-excavationSkill
- assumption-extractionSkill
- ballot-collectionSkill
- best-option-selectionSkill
- bottleneck-identificationSkill
- category-sortingSkill
- cluster-analysisSkill
- coherence-diagnosisSkill
- collective-adjudicationSkill
- comparative-feasibility-rankingSkill
- comparison-executorSkill
- conclusion-sensitivitySkill
- conjunctive-filterSkill
- consensus-classificationSkill
- consensus-measurementSkill
- consensus-synthesisSkill
- consistency-audit-loopSkill
- constraint-classificationSkill
- constraint-drillingSkill
- constraint-identificationSkill
- constraint-identification-sopSkill
- convergence-checkSkill
- convergence-distillationSkill
- counter-thesis-constructionSkill
- coverage-scoringSkill
- criteria-interrogationSkill
- criterion-definitionSkill
- critic-attackSkill
- cycle-detectionSkill
- deliberative-calibrationSkill
- dimension-assessmentSkill
- disagreement-cartographySkill
- disagreement-mappingSkill
- disagreement-visualizationSkill
- diversity-maximizationSkill
- dominance-checkSkill
- dynamic-trackingSkill
- efficient-explorationSkill
- feasibility-synthesisSkill
- feedback-distributionSkill
- full-rankingSkill
- futures-calibrationSkill
- gate-criteria-definitionSkill
- gate-judgmentSkill
- inconsistency-localizationSkill
- iterative-convergence-roundSkill
- judge-verdictSkill
- judgment-collectionSkill
- maturation-pathway-designSkill
- maturity-diagnosisSkill
- method-sensitivity-reportSkill
- The first 60 shown.
The file
Files
Feasibility Assessment
Evaluate whether selected research candidates can actually be implemented. This campaign applies Technology Readiness Levels (TRL), NASSS complexity framework, Stage-Gate processes, TRIZ contradiction analysis, Theory of Constraints (TOC), and parametric estimation to determine real-world viability before committing resources.
Strategy Routing
| Signal | Strategy |
| assess readiness level / maturity / TRL | maturity-diagnosis |
| identify blockers / constraints / showstoppers | constraint-identification |
| estimate resources / budget / timeline | resource-envelope-estimation |
| compare feasibility across candidates | comparative-feasibility-ranking |
| design maturation path / roadmap to readiness | maturation-pathway-design |
Manifest
Strategies
| Strategy | Description |
| maturity-diagnosis | Assess current readiness using TRL 9-level, NASSS 7-dimension, and Innovation Readiness Level frameworks |
| constraint-identification | Find blockers using TOC, TRIZ contradiction analysis, and Pre-mortem techniques |
| resource-envelope-estimation | Estimate resources using parametric, analogous, and three-point (PERT) estimation |
| comparative-feasibility-ranking | Compare candidates using multi-dimensional radar and weighted feasibility index |
| maturation-pathway-design | Design path to readiness using Stage-Gate, Technology Roadmapping, and milestone planning |
Tactics
| Tactic | Description |
| multi-dimensional-readiness-scan | Assess each dimension, synthesize radar, identify bottlenecks |
| constraint-drilling | Identify constraints, classify, assess removability, design removal path |
| staged-gate-evaluation | Define gate criteria, evaluate at each gate, render go/kill/recycle decision |
SOPs
| SOP | Description |
| dimension-assessment | Score a single readiness dimension with evidence and gap analysis |
| radar-synthesis | Synthesize dimension scores into radar chart data and overall readiness |
| bottleneck-identification | Identify bottlenecks from radar data with severity ranking |
| constraint-identification-sop | Identify constraints for a candidate in context |
| constraint-classification | Classify constraints into hard, soft, and assumptions |
| removability-assessment | Assess removability of a constraint with effort estimate |
| removal-path | Design removal steps with timeline and resource needs |
| gate-criteria-definition | Define gate criteria and pass thresholds for a stage |
| gate-judgment | Render GO/KILL/RECYCLE verdict with evidence |
| feasibility-synthesis | Synthesize all assessments into feasibility matrix and recommendation |
Budget Table
| Metric | Target |
| Dimensions assessed | >= 5 (technical, market, regulatory, resource, organizational) |
| Blockers identified | >= 3 per candidate |
| Estimate precision | from +/-30% to +/-10% through iteration |
| Gates evaluated | >= 3 stage gates |
MCP Tools
vault_search— find prior feasibility assessments and readiness datavault_query_graph— traverse relationships between candidates and constraintsvault_add_edge— link feasibility findings to candidatessemantic-scholar— retrieve technical maturity evidence from literature
Context Management
State is maintained in the campaign ledger with keys:
candidates[]— items under feasibility assessmentdimension_scores{}— readiness scores per dimension per candidateconstraints{}— identified constraints per candidategate_verdicts{}— stage-gate decisionsfeasibility_matrix— final comparative matrix
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.