signalproof-plan

Converts ambiguous requests into bounded, evidence-aware execution plans with acceptance criteria and rollback paths.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-plan-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-plan
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-plan
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-plan-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Consequential work often starts before objectives, scope, protected state, and authority are clear, leading to uncontrolled changes, broken working systems, and unverifiable results. This Skill turns an ambiguous or high-stakes request into a bounded execution plan that another human or agent can follow without guessing. ## Core Features & Use Cases - Structured Planning Contract: Enforces objective definition, evidence classification, protected state declaration, scope boundaries (required / allowed / out-of-scope), and authority checks before any implementation begins. - Acceptance and Recovery Design: Produces an acceptance matrix with testable pass conditions, rollback targets, and explicit STOP conditions that halt execution when assumptions fail or scope expands. - Plan Status Gating: Returns a clear status such as READY, INVESTIGATE FIRST, AWAITING AUTHORITY, or BLOCKED so consequential actions never proceed without proper authorization. - Use Case: Before refactoring a production authentication module, use this Skill to document current behavior, forbid changes to working session handling, define verification tests, and set a rollback point so a builder can execute safely. ## Quick Start Ask the AI to create a Signalproof plan for your upcoming change, including scope boundaries, protected state, acceptance criteria, and rollback steps before any code is written.

Frequently Asked Questions about signalproof-plan

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

FAQPage Schema
How do I plan a software change before writing code?▼

Define the outcome-shaped objective, establish current state from evidence, declare protected state that must not regress, and set required versus out-of-scope boundaries. Then add an acceptance matrix, recovery path, and STOP conditions before any implementation begins.

What should a technical implementation plan include?▼

A complete plan includes the objective, evidence-classified current state, protected state, scope boundaries, authority status, dependencies, ordered change steps, an acceptance matrix, rollback strategy, and STOP conditions. It should be executable by another person without silent interpretation.

When should a plan be marked as blocked or investigate first?▼

Mark INVESTIGATE FIRST when a material unknown prevents responsible planning, and BLOCKED when environment, dependency, or evidence gaps make a viable plan impossible. Use AWAITING AUTHORITY when a consequential action lacks explicit human approval.

How do I define acceptance criteria for a code change?▼

For each material requirement, specify how it will be tested, the observable pass condition, and what evidence will be retained. Distinguish compile, automated, runtime, visual, security, and release gates rather than using subjective criteria like looks good.

When should I not use a formal planning workflow?▼

Skip heavyweight planning for trivial, low-risk, fully reversible changes where current state is obvious and no protected behavior exists. The planning contract is designed for ambiguous or consequential work where verification and recovery matter.