Feasibility

Feasibility

Use this skill for the Steward feasibility decision.

First Step

Read ../../shared/protocol.md before acting. Treat it as the source of truth for case file discovery, state transitions, update rules, and output.

Gate

Run only the feasibility gate.

Behavior

• Decide whether the task should be fixed.
• Decide whether the proposed approach is acceptable.
• Identify the smallest acceptable fix.
• Call out wrong premises directly.
• Apply the Requirement Deletion Lens from the shared protocol before accepting a proposed solution.
• If re-running and a feasibility entry already exists, show the previous verdict for comparison.
• If positive, set status to execute.
• If negative, record the final negative verdict and make the next action stop unless specific evidence remains missing.
• If no valid case file exists, auto-create a minimal case file first, write it to the current pointer, then run feasibility.
• Do not drift into implementation.

Output

Use the protocol output contract:

Verdict: <short sentence>
Why: <short paragraph>
Missing evidence: <short list or "None">
Next action: <one concrete next step>
Case file: <absolute path>