skills.rest
Corvalis-LLC
Corvalis-LLCOFFICIAL
Explore all skills by this author →
GitHub

plan-validate

Validate multi-stream implementation plans for unique IDs, dependencies, and ownership.

6|Updated Mar 31, 2026
Search Tags:#workflow#validation#dependencies#verification#plan#streams
One-click install
npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill plan-validate-corvalis-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-validate
Source: https://github.com/Corvalis-LLC/Crow-Stack/tree/main/skills/plan-validate
Command: npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill plan-validate-corvalis-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate multi-stream implementation plans before /stream or /dominion execution to catch structural and ownership issues early.

Core Features & Use Cases

  • Check stream structure: unique IDs, clear titles, valid sub-streams
  • Validate dependencies and ownership: ensure no cycles and concrete owners
  • Verify metadata: Required Skills present and final validation mode specified
  • Use Case: Before handing off a plan, review it to prevent downstream failures during automation streams

Quick Start

Review a generated plan file and confirm that all streams are uniquely identified and dependencies are coherent before proceeding to /stream or /dominion.

Frequently Asked Questions about plan-validate

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

FAQPage Schema
How do I validate multi-stream implementation plans before execution?▼

Validating multi-stream plans requires checking unique stream IDs, coherent dependencies, and explicit ownership before execution. This review process catches structural and ownership issues early to prevent downstream failures during automation streams.

What issues should I check for when reviewing a plan with multiple streams?▼

When reviewing a multi-stream plan, check for unique stream IDs, clear titles, valid sub-streams, dependency cycles, and concrete ownership. You must also verify required metadata like final validation mode and verified skill ownership to surface actionable gaps.

Why does my multi-stream plan fail during automation execution?▼

Multi-stream plans fail during automation execution due to unresolved structural and ownership issues. Validating the plan beforehand enforces metadata requirements, ensures coherent dependencies, and surfaces actionable gaps to prevent these downstream failures.

Do I need to specify a final validation mode in my stream plan metadata?▼

Yes, you need to specify a final validation mode in your stream plan metadata. The validation process enforces metadata requirements, including final validation mode and verified skill ownership, to ensure plans execute without structural failures.

Can I validate manually edited implementation plans before running streams?▼

Yes, you can validate manually edited implementation plans before running streams. Apply validation during plan review to ensure manually edited or generated plans maintain unique stream IDs, coherent dependencies, and explicit ownership before execution.

Related Skills

Explore More Software Engineering Skills→
Shakes-tzdShakes-tzd
3

htmlgraph

Coordinate HtmlGraph session tracking and multi-agent orchestration with the Python SDK.

Community
Advanced
dadbodgeoffdadbodgeoff
783

sse-resilience

Manage SSE streams with Redis-backed persistence, heartbeat monitoring, and cleanup.

Community
Advanced
PaulKinlanPaulKinlan
2

task-decomposition

Decompose high-level goals into actionable tasks with owners and dependencies.

Community
Advanced
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate