px-plan

Converts brainstormed idea files into phased implementation plans with research summaries.

22|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/DFilipeS/praxis --skill px-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: px-plan
Source: https://github.com/DFilipeS/praxis/tree/main/praxis/skills/px-plan
Command: npx skills add https://github.com/DFilipeS/praxis --skill px-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts informal brainstorm idea files into precise, actionable implementation plans that remove ambiguity and prepare the work for focused implementation, review, and commit.

Core Features & Use Cases

  • Idea-driven planning: Requires idea files from .ai-workflow/ideas/ and turns them into one or more plan files, each representing a single deliverable phase.
  • Research orchestration: Launches three parallel Task sub-agents (codebase-explorer, knowledge-reviewer, external-researcher) and synthesizes their summaries to inform scope, dependencies, and acceptance criteria.
  • Concrete, reviewable plans: Produces plan files using the provided template with structured frontmatter, explicit steps that reference file line ranges, acceptance criteria, dependencies, and related documents, then updates idea metadata and offers to stage commits.
  • Behavioral guardrails: Enforces "never write code" during planning, insists on minimum ambiguity, and splits large work into independently valuable phases.

Quick Start

Create a plan from the idea file .ai-workflow/ideas/20260222-offline-first-sync.md including phased steps, acceptance criteria, referenced file line ranges, and a research summary.

Frequently Asked Questions about px-plan

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

FAQPage Schema
How do I turn brainstormed ideas into actionable implementation plans?

This Skill converts brainstormed idea files from the .ai-workflow/ideas directory into concrete implementation plans. It outputs structured plan files representing single deliverable phases with explicit steps, acceptance criteria, and file line-range directives.

How does research orchestration work for software planning?

Research orchestration launches three parallel Task sub-agents: a codebase-explorer, a knowledge-reviewer, and an external-researcher. It synthesizes their summaries to inform project scope, dependencies, and acceptance criteria.

Can I generate implementation plans without writing code during the planning phase?

Yes, the planning workflow enforces a strict behavioral guardrail to never write code during planning. It insists on minimum ambiguity and splits large work into independently valuable phases for focused implementation and review.

Does the planning workflow support git staging for plan files?

Yes, the workflow supports git staging per repository conventions. After updating idea and plan metadata, it offers to stage commits to prepare the structured plan files for version control.

What is the best way to structure deliverable phases for software implementation?

The best way to structure deliverable phases is using a plan file template with structured frontmatter. This template organizes explicit steps, acceptance criteria, dependencies, and related documents to split large work into independently valuable phases.