spp-editor

Normalize SPP planning cards to preserve valid codex_plan statuses.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill spp-editor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spp-editor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/spp-editor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill spp-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bounded editing of SPP planning cards to preserve truthful planning state, fix drift, and ensure valid codex_plan statuses before execution.

Core Features & Use Cases

  • Normalize and repair SPP planning cards to reflect issue-local prompts, dependencies, and review hooks.
  • Tighten scope, stop conditions, and references to prevent drift and improve planning fidelity.
  • Support bounded edits only, avoiding execution-state manipulation, and generate a clear handoff for review.

Quick Start

Edit an SPP planning card to align with the current issue prompt and approved plan, stopping before execution.

Frequently Asked Questions about spp-editor

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

FAQPage Schema
How do I fix drift in markdown planning cards before execution?

To fix drift in markdown planning cards, normalize the SPP frontmatter and sections to align with issue prompts and approved plans. This preserves truthful planning state and ensures valid statuses before execution.

What is SPP planning card normalization for software engineering?

SPP planning card normalization is the process of editing and aligning markdown planning boundaries, issue prompts, and dependencies to preserve truthful state. It ensures frontmatter conforms to the canonical schema and prevents scope drift.

How do I edit SPP frontmatter to ensure valid codex_plan statuses?

Edit SPP frontmatter by applying safe, bounded edits to source references and dependencies. This stops before execution-state manipulation, ensuring valid codex_plan statuses and generating a clear handoff for review.

Can I use bounded edits to tighten scope and stop conditions in planning markdown?

Yes, you can use bounded edits to tighten scope, stop conditions, and references in planning markdown. This prevents drift, improves planning fidelity, and strictly avoids execution-state manipulation.

Why does my SPP planning card fail schema verification?

SPP planning cards fail schema verification due to drift between the planning state and issue-local prompts. Normalizing the frontmatter and sections to match the canonical schema fixes these inconsistencies and ensures readiness.

Does the SPP editor modify execution state or just planning boundaries?

The SPP editor only modifies planning boundaries and does not alter execution state. It applies bounded edits to normalize cards, preserve truthful planning state, and generate a clear handoff for review before execution.