goal-prompt-builder

To convert vague project requests into structured /goal commands, this skill uses a deterministic 5-section template covering Objective, Scope, Constraints, Done when, and Stop if. It translates fuzzy inputs into audit-friendly prompts to prevent scope creep.

An audit-friendly /goal prompt is a standardized command formatted with Objective, Scope, Constraints, Done when, and Stop if sections. You need one when executing automation workflows to prevent misalignment and ensure verifiable scope boundaries during project execution.

Yes, the goal prompt builder auto-detects project type from the filesystem or repo URL. It identifies environments like Node, Python, Swift, Go, Rust, or static sites to accurately tailor the generated constraints and stop conditions for your specific project.

To load project-specific constraints from AGENTS.md and CLAUDE.md, the skill automatically reads these files when present in your repository. It integrates these rules directly into the generated /goal command to tailor constraints for your workflow.

The best way to prevent scope creep when generating workflow automation templates is to enforce deterministic boundaries using the 5-section template. By defining explicit Stop if and Done when conditions, the prompt restricts unapproved actions during execution.

Yes, you can generate a goal prompt without detailed specifications by providing a vague request like 'help me write a goal'. The skill walks through mode selection, project detection, and scenario choice to produce a precise, copy-pasteable /goal command.