p

Coordinate planner-driven tasks across registry shards with phased gate checks.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ipswitch8/CC_tools --skill p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: p
Source: https://github.com/ipswitch8/CC_tools/tree/main/skills/p
Command: npx skills add https://github.com/ipswitch8/CC_tools --skill p

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines planning and execution by coordinating planner-driven tasks across registry shards, ensuring the pipeline is loaded, validated, and executed in phases with gate checks.

Core Features & Use Cases

  • Planner-driven task orchestration: invoke the planner with the provided task description and load the generated pipeline.json.
  • Phased execution with gates: run each phase in order and validate gate agents before proceeding.
  • Robust loading: always load the pipeline and meta shards; load additional shards based on the domain.

Quick Start

Provide a task description and let the system generate and execute the corresponding pipeline.

Frequently Asked Questions about p

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

FAQPage Schema
How do I execute phased pipelines with gate checks between stages?

Phased pipelines execute sequentially by running each phase in order and validating gate agents before proceeding to the next stage. This approach enforces loading the pipeline configuration and applies gate verification between phases to ensure structured task completion.

What is planner-driven task orchestration for automation workflows?

Planner-driven task orchestration invokes a planner with a task description to generate and load a pipeline configuration file. It coordinates execution across registry shards, ensuring the generated pipeline is loaded, validated, and executed in defined phases with gate checks.

How do I load and select registry shards for domain-specific execution?

Registry shard selection always loads pipeline and meta shards first, then dynamically loads additional shards based on the specific domain. This ensures correct shard selection and robust loading for executing the targeted automation workflow.

When do I need plan-driven execution for automation workflows?

Plan-driven execution is needed for workflows that require phased work with gates and verification between phases. It coordinates planner-driven tasks across registry shards to complete complex operations requiring structured, sequential phase execution with validation.

Does plan-driven pipeline execution require any external dependencies?

Plan-driven pipeline execution operates without external dependencies, relying entirely on internal coordinator, planner, and registry shard mechanisms to load configurations and enforce sequential phase execution with gate checks.