ScopePrompt

Turn a rough software idea into a task an agent can actually finish.

ScopePrompt creates one scoped, testable development prompt with explicit boundaries, phased verification, and evidence requirements.

See how it works Review v0.1.0 scope

A good coding task needs more than a feature sentence.

What must change What must not change How completion is proved

From intent to executable brief

ScopePrompt adjusts the brief for a new project, an existing-project feature, a bugfix, or a behavior-preserving refactor.

  1. 01

    Find the outcome

    Identify the user-visible or engineering result that matters.

  2. 02

    Set the boundary

    State delivery scope, non-goals, and any authorization limits.

  3. 03

    Plan the work

    Break the task into phases that fit the project type and available evidence.

  4. 04

    Require proof

    Define realistic checks and an Evidence Report before completion is claimed.

One prompt, with the decisions made explicit.

The result is designed to be copied into a fresh Codex task. It avoids inventing repository files or commands when the project has not been inspected.

development-task.md

ObjectiveShip the smallest complete outcome.

Delivery boundaryIncluded behavior and explicit non-goals.

Implementation phasesInspect → change → verify.

Acceptance criteriaObservable, testable completion conditions.

Evidence ReportCommands, results, gaps, and remaining risk.

Small by design in v0.1.0

The first release is a skills-only plugin. Its job is to create the brief, not to execute the development work.

External APIs
None
ScopePrompt account
Not required
Publisher data storage
None
MCP server
Not included

ChatGPT or Codex may process your conversation under the platform's own terms and privacy controls. ScopePrompt does not operate a separate processing backend for v0.1.0.

Clarity before code.

ScopePrompt helps turn an ambiguous request into work that can be reviewed, verified, and handed off.

Contact support