pi-project

Validate project state blocks against typed JSON schemas.

25|4|Updated Mar 13, 2026

Search Tags:#workflow #planning #validation #schema #lifecycle #blocks #project

Ready to run

npx skills add https://github.com/davidorex/pi-project-workflows --skill pi-project

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pi-project
Source: https://github.com/davidorex/pi-project-workflows/tree/main/packages/pi-project/skills/pi-project
Command: npx skills add https://github.com/davidorex/pi-project-workflows --skill pi-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Schema-driven project state management for structured, validated blocks that enforce cross-block referential integrity and lifecycle planning within .project/.

Core Features & Use Cases

Validates writes against JSON Schemas for each block (project, tasks, decisions, domain, etc.).
Supports a planning lifecycle with derived state, references, and cross-block consistency checks.
Provides tooling to initialize, read, write, and validate blocks, ensuring atomicity and schema conformance.

Quick Start

Initialize the .project directory to bootstrap schemas and blocks and then run /project status to inspect the current state.

Frequently Asked Questions about pi-project

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

FAQPage Schema

How do I validate JSON schema for project state blocks in a .project directory?▼

Schema-driven project state validation checks typed JSON blocks like project.json and tasks.json against predefined schemas, enforcing data integrity and cross-block referential consistency before writes are committed. This ensures lifecycle planning and state accuracy.

What is JSON schema-based project lifecycle management and when do I need it?▼

JSON schema-based project lifecycle management coordinates state blocks like decisions.json and verification.json to derive status and enforce planning consistency. You need it when your project requires structured, validated state transitions and cross-block referential integrity within a .project directory.

How do I initialize a .project directory with typed JSON schemas and blocks?▼

To initialize a .project directory, run the bootstrap process to generate typed JSON schemas and state blocks like project.json and tasks.json. After initialization, inspect the current derived state and lifecycle status using the project status command.

Can I enforce cross-block referential integrity between tasks and decisions?▼

Yes, cross-block referential integrity is enforced by validating writes against JSON schemas, ensuring that state blocks like tasks.json and decisions.json maintain consistency and that derived status and references align across the entire project lifecycle.

Does pi-project support atomic schema-based writes for project state blocks?▼

Yes, pi-project supports atomic schema-based writes, ensuring that updates to state blocks like project.json and verification.json conform to typed JSON schemas and maintain data integrity during the planning lifecycle without partial updates.

What are the limitations of schema-driven validation for project state management?▼

Schema-driven project state management is limited to projects organizing state in a .project directory with specific JSON blocks like project.json and tasks.json, meaning it may not suit projects with unstructured state or those not using typed JSON schemas for lifecycle planning.