implementing-plans

Name: implementing-plans
Availability: InStock
Author: ReadyStateChange

Execute approved plans phase-by-phase with contract tests and verification.

Updated Mar 8, 2026

Search Tags:#workspace #parallelization #governance #specification-driven #plan-execution #phase-management #contract-tests

Ready to run

npx skills add https://github.com/ReadyStateChange/agents --skill implementing-plans-readystatechange

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementing-plans
Source: https://github.com/ReadyStateChange/agents/tree/main/skills/implementing-plans
Command: npx skills add https://github.com/ReadyStateChange/agents --skill implementing-plans-readystatechange

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing approved specifications by executing plans phase-by-phase with verification. The plan organizes the work, but the specification governs the behavior.

Core Features & Use Cases

Phase-by-phase execution of approved plans with verification and contract tests.
Governance-aligned progression: respecting plan chunks, dependencies, and parallelizable workstreams.
Workspace hygiene and bookmarking strategy: ensuring clean starts and traceable progress between phases.

Quick Start

Load the plan path and start with the earliest unchecked phase whose dependencies are satisfied.

Frequently Asked Questions about implementing-plans

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

FAQPage Schema

How do I execute a software development plan phase-by-phase with verification?▼

Phase-by-phase plan execution works by loading an approved plan path and starting at the earliest unchecked phase whose dependencies are met, verifying each step with contract tests. This ensures clean working copies and traceable progress between phases.

What is specification-driven plan execution in software projects?▼

Specification-driven plan execution organizes work using a plan while a governing specification defines the required behavior. This enforces contract-based tests, phase-driven progression, and strict dependency management across parallelizable workstreams.

How do I manage parallel workstreams and dependencies during plan execution?▼

You manage parallel workstreams during plan execution by respecting plan chunks and dependencies, ensuring governance-aligned progression. The system allows phase-driven progression only when phase dependencies are satisfied, maintaining workspace hygiene across parallel tasks.

Do I need contract tests to use phase-driven progression for software implementation?▼

Yes, contract-based tests are required for phase-driven progression. This approach applies specifically to software projects needing contract tests, phase test checklists, and clean-working-copy discipline to verify behavior against an approved specification.

What's the best way to maintain workspace hygiene between execution phases?▼

Maintain workspace hygiene between execution phases by applying a bookmarking strategy that ensures clean starts and traceable progress. This clean-working-copy discipline prevents leftover artifacts from disrupting subsequent phase execution and contract test verification.

When should I avoid using specification-driven plan execution?▼

Avoid specification-driven plan execution for software projects that do not require contract-based tests or strict phase dependency management. Without an approved specification governing behavior and a structured plan organizing work chunks, the phase-by-phase verification overhead provides little value.