Come usare
- Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
- Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
- Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill assess-goal-feasibilityPrima di iniziare
- L’installazione non include abbonamenti, quote API o accesso ai file.
- Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale
Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.
assess-goal-feasibility
Purpose
Cross-check goal branches against resources, obstacles, and timeline; label each feasible, stretch, or infeasible and propose OR alternatives.
Input contract
yaml
required: [goal_branches, resource_profile, obstacle_register, timeline]
optional: [capability_evidence, dependency_graph, alternative_constraints]
constraints: [each branch must have explicit resource, obstacle, and deadline checks]Procedure
- Decompose each branch into deliverables, dependencies, and required capabilities.
- Compare requirements with resources and obstacle severity.
- Test schedule against dependencies and deadline; assign feasible/stretch/infeasible.
- For infeasible branches, construct OR alternatives that relax a declared constraint.
If the goal is feasible and its remaining tradeoffs are resolved, consider crystallize-north-star as the next tactic.
Output contract
yaml
produces: [feasibility_matrix, blocking_obstacles, alternative_branches, timeline_rationale]
delta_fields: [findings, decisions, open_questions, recommended_jumps]Quality gates
- Every branch receives all three labels checks: resource, obstacle, timeline.
- Infeasible labels identify a blocking condition and evidence.
- Each OR alternative states the relaxed constraint and residual risk.
Parameterization
Caller supplies branch schema, resource dimensions, obstacle scale, timeline units, feasibility labels, and OR-generation policy.
Failure and counterexamples
Do not label a branch feasible when an unbounded dependency or missing capability is unexamined.
Provenance map
- resolved: feasibility-check
