maturation-pathway-design
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Design path to readiness using Stage-Gate, Technology Roadmapping, and milestone planning 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-assessmentSkill
- feasibility-synthesisSkill
- feedback-distributionSkill
- full-rankingSkill
- futures-calibrationSkill
- gate-criteria-definitionSkill
- gate-judgmentSkill
- inconsistency-localizationSkill
- iterative-convergence-roundSkill
- judge-verdictSkill
- judgment-collectionSkill
- maturity-diagnosisSkill
- method-sensitivity-reportSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Place milestones within each stage as progress indicators
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Maturation Pathway Design
Purpose: Given a candidate that is not yet ready, design a concrete pathway to bring it to implementation readiness. Uses Stage-Gate processes to define decision points, Technology Roadmapping to sequence development activities, and milestone planning to create actionable checkpoints.
When to use:
- A candidate has potential but is not yet mature enough for implementation
- Stakeholders need a roadmap showing how and when readiness can be achieved
- You need to define clear gates and milestones for a maturation effort
Budget
| Metric | Target |
| Stage gates defined | >= 3 |
| Milestones per stage | >= 2 |
| Resource estimates per stage | 1 per stage |
State Ledger
| Key | Type | Description |
| candidate | object | The candidate needing maturation |
| current_readiness | object | Starting maturity profile |
| target_readiness | object | Required maturity for implementation |
| stages[] | array | Defined maturation stages |
| gates[] | array | Decision gates between stages |
| milestones[] | array | Checkpoints within stages |
| roadmap | object | Complete maturation roadmap |
Available Tactics
| Tactic | When |
| staged-gate-evaluation | To define and evaluate gates along the maturation path |
| multi-dimensional-readiness-scan | To assess readiness at each stage |
Available SOPs
| SOP | Purpose |
| gate-criteria-definition | Define criteria for each gate |
| gate-judgment | Evaluate readiness at each gate |
| dimension-assessment | Assess dimension readiness at checkpoints |
| feasibility-synthesis | Synthesize pathway into overall feasibility view |
Execution Guidance
- Establish current readiness profile (from maturity-diagnosis output)
- Define target readiness required for implementation
- Identify the gap between current and target across all dimensions
- Design stages that progressively close the gap
- Define gate criteria for transitions between stages
- Place milestones within each stage as progress indicators
- Estimate resources and timeline for each stage
- Identify critical path and dependencies between stages
Output Format
maturation_pathway:
candidate: <name>
current_readiness: <overall score>
target_readiness: <required score>
gap_dimensions: [{dimension, current, target, gap}]
stages:
- stage: 1
name: <stage name>
objective: <what this stage achieves>
milestones: [{name, criteria, target_date}]
resources: {time, cost, personnel}
gate:
criteria: [...]
pass_threshold: <condition>
total_timeline: <duration>
total_cost: <estimate>
critical_path: [<stage dependencies>]
risk_factors: [{risk, mitigation, stage_affected}]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.

