replan

Integrate review findings or manual edits into versioned plan artifacts.

4|Updated Mar 23, 2025

Search Tags:#versioning #implementation #review #audit-log #feature-plan #replan

Ready to run

npx skills add https://github.com/matochu/pythia --skill replan-matochu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: replan
Source: https://github.com/matochu/pythia/tree/main/.agents/skills/replan
Command: npx skills add https://github.com/matochu/pythia --skill replan-matochu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Revising a feature plan after review findings, implementation issues, or manual edits while preserving a complete history.

Core Features & Use Cases

Orchestrates replan workflows by interpreting inputs, locating the correct plan, and applying changes without breaking version history.
Supports three trigger modes: review-driven (R), implementation-driven (I), and manual edits, with gated validation and an audit log.
Generates a structured Plan revision log and appends an Architect retrospective for future cycles.

Quick Start

Provide a feature ID and the target trigger (e.g., feat-2026-01-123 from R2) to initiate a replan.

Frequently Asked Questions about replan

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

FAQPage Schema

How do I revise a feature plan after implementation issues while keeping an audit log?▼

To revise a feature plan after implementation issues, trigger an implementation-driven replan to integrate findings into a new versioned plan artifact. The process updates the Plan revision log with a fresh entry to maintain a complete audit history.

What is the best way to incorporate review findings into an existing feature plan?▼

Incorporating review findings uses a review-driven replan trigger to amend the feature plan stored under plans/{plan-slug}.plan.md. New or amended steps include explicit version markers to ensure changes are fully auditable.

Can I manually edit a feature plan without breaking the version history?▼

Yes, manual edits are supported as a distinct trigger mode for updating a feature plan. The replan workflow applies your changes while preserving version history and appending a fresh entry to the Plan revision log.

How do I start a replan workflow for a specific feature?▼

Start a replan workflow by providing a feature ID and the target trigger, such as feat-2026-01-123 from R2. The skill locates the correct plan artifact and applies gated validation before generating the amended versioned plan.

What happens after updating a feature plan with a new versioned artifact?▼

After updating a feature plan, a validation step is performed in a separate flow to verify the artifact. An Architect Retrospective may also be appended to the new plan to provide insights for future development cycles.

Does the replan workflow validate required artifacts before applying review rounds?▼

Yes, explicit gating validates required artifacts for review and implementation rounds before changes are applied. This ensures the feature plan exists and meets criteria before generating a new versioned plan artifact.