agentleFS
Sign inStart free
PthahnixPthahnix/De-Anthropocentric-Research-Engine/skills/assess-goal-feasibility/SKILL.md

assess-goal-feasibility

Skill504 starsChanged 50 days agoApache-2.0View on GitHub

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

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Test schedule against dependencies and deadline.

    line 21
  2. Very specific:

    If the goal is feasible and its remaining tradeoffs are resolved, consider crystallize-north-star as the next tactic.

    line 24
  3. Distinctive:

    Every branch receives all three labels checks: resource, obstacle, timeline.

    line 33
  4. Distinctive:

    Do not label a branch feasible when an unbounded dependency or missing capability is unexamined.

    line 41

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

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

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free