yogsoth-ai/de-anthropocentric-research-engine

assess-goal-feasibility

Cross-check goal branches against resources, obstacles, and timeline; label feasible/stretch/infeasible and propose OR alternatives.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill assess-goal-feasibility

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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

  1. Decompose each branch into deliverables, dependencies, and required capabilities.
  2. Compare requirements with resources and obstacle severity.
  3. Test schedule against dependencies and deadline; assign feasible/stretch/infeasible.
  4. 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

Related by task

from this repository

More skills

All skills