goal-backward

Derive observable truths and required artifacts from stated goals.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill goal-backward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-backward
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/goal-backward
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill goal-backward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Goal-backward thinking derives observable truths, required artifacts, wiring, and key links from a stated goal to create concrete must-haves for plans and verification.

Core Features & Use Cases

  • Step 0: Extract Requirement IDs (planner only)
  • Step 1: State the Goal
  • Step 2: Derive Observable Truths
  • Step 3: Derive Required Artifacts
  • Step 4: Derive Required Wiring
  • Step 5: Identify Key Links
  • The methodology is applied by Planner, Verifier, Plan-checker, and Roadmapper to produce structured outputs that guide plan validation and success criteria.

Quick Start

Run the Goal-backward process against ROADMAP.md to generate the truths, artifacts, wiring, and links that define the success criteria for the next phase.

Frequently Asked Questions about goal-backward

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I derive observable truths and required artifacts from a project goal?

To derive observable truths and artifacts from a project goal, apply backward reasoning to extract testable criteria, required wiring, and key links that define success for planning and verification workflows.

What is backward reasoning for goal success in roadmapping?

Backward reasoning for goal success is a methodology that translates stated goals into structured outputs including truths, artifacts, wiring, and links to guide plan validation and roadmapping across project phases.

How do I generate testable success criteria from a ROADMAP.md file?

Generate testable success criteria from a ROADMAP.md file by running a backward reasoning process to extract observable truths, required artifacts, and wiring that define the validation criteria for the next phase.

Can I use goal-backward planning for both plan formation and verification?

Yes, goal-backward planning applies to both plan formation and verification workflows, enabling planners, verifiers, and plan-checkers to translate goals into structured outputs consumed by downstream tooling.

Does backward goal planning require external dependencies or components?

No, backward goal planning requires no external dependencies or components, operating independently to derive structured truths, artifacts, wiring, and key links from stated goals for downstream checks.