evolution-constraint-planner

Enforce a plan-code-achieve loop that freezes meaning before coding.

7|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Etherstrings/evolution-constraint-planner --skill evolution-constraint-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution-constraint-planner
Source: https://github.com/Etherstrings/evolution-constraint-planner/tree/main
Command: npx skills add https://github.com/Etherstrings/evolution-constraint-planner --skill evolution-constraint-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Evolution Constraint Planner enforces a disciplined plan/code/achieve loop that freezes meaning before coding, preventing semantic drift on complex requests.

Core Features & Use Cases

  • Structured, stage-gated workflow from raw request to archived closure.
  • Code is executed strictly from a frozen handoff, with independent critique and adversarial review stages.
  • Supports OpenSpec exports and a full bundle of companion docs for verification, testing, and traceability.

Quick Start

Use this skill to turn a raw product or engineering request into a code-ready bundle that can be planned, coded, and closed with evidence.

Frequently Asked Questions about evolution-constraint-planner

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

FAQPage Schema
How do I prevent semantic drift when planning complex engineering requests?

To prevent semantic drift on complex engineering requests, enforce a strict plan-code-achieve loop that freezes meaning before coding begins. This stage-gated workflow requires aggressive clarification and dependency-aware planning to lock down requirements.

How do I turn raw product requests into code-ready delivery bundles?

Turn raw product requests into code-ready delivery by processing them through a structured workflow that outputs a frozen handoff bundle. This bundle includes explicit constraints, verification steps, and companion docs for traceability.

What is a frozen handoff in software delivery planning?

A frozen handoff in software delivery planning is a locked specification document that code execution strictly follows. It prevents scope changes mid-implementation by requiring independent critique and adversarial review stages before coding starts.

Does the Evolution Constraint Planner support OpenSpec exports?

Yes, the Evolution Constraint Planner supports OpenSpec exports. It generates a full bundle of companion docs for verification, testing, and traceability to ensure comprehensive staged delivery and archival closure.

Can I use dependency-aware planning for browser checks and verification?

Yes, dependency-aware planning includes explicit constraints, verification steps, and browser checks. This ensures complex product and engineering requests undergo staged delivery with evidence before reaching archival closure.

When should I use a stage-gated workflow for code execution?

Use a stage-gated workflow for code execution when handling complex product and engineering requests that benefit from aggressive clarification. It enforces a strict plan-code-achieve loop with independent critique and adversarial review to prevent semantic drift.