plan

Convert vague data goals into phased workflows with verification criteria.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Soria-Inc/soria-stack --skill plan-soria-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Soria-Inc/soria-stack/tree/main/plan
Command: npx skills add https://github.com/Soria-Inc/soria-stack --skill plan-soria-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan generation converts vague data goals into concrete, phased workflows with explicit verification criteria, preventing ad-hoc or misaligned planning.

Core Features & Use Cases

  • Phase-based planning that yields actionable steps for Extract → Transform → Value-map → Load → Represent cycles.
  • Prerequisite checks and routing to downstream skills (status, ingest, map, dive, verify, newsroom) based on user intent.
  • Artifact-first governance that requires formal approval before execution and records decisions for reproducibility.

Quick Start

Provide a plan for a defined data goal and I will produce a detailed, verifiable plan including environment, goals, phase statuses, sequencing, and decision points.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I structure a vague data goal into a phased data pipeline workflow?

Phased data pipeline planning converts vague directives into concrete Extract, Transform, Value-map, Load, and Represent cycles with explicit verification criteria and sequencing.

What is plan generation for data orchestration and how does it work?

Plan generation formalizes data orchestration by producing a formal artifact that gates execution until approval, routing prerequisites to downstream skills and documenting decisions for reproducibility.

How do I add verification criteria to my data pipeline status checks?

Add verification criteria to data pipeline status checks by generating a formal plan artifact that defines phase statuses, decision points, and explicit prerequisites before execution begins.

Can I route my data pipeline tasks to downstream skills based on user intent?

Yes, you can route data pipeline tasks to downstream skills like status, ingest, map, dive, verify, and newsroom based on user intent through prerequisite checks and formal plan routing.

What are the limitations of ad-hoc planning for data pipelines?

Ad-hoc planning for data pipelines lacks formal governance, explicit prerequisites, and verifiable phase sequencing, which can lead to misaligned execution and unreproducible data decisions.

Does the plan skill require approval before executing data pipeline phases?

Yes, the plan skill enforces artifact-first governance by requiring formal approval before execution, ensuring all phased actions, environment details, and decision points are documented for reproducibility.