zero-to-documented

Builds and documents pi extensions through a seven-phase plan-to-install workflow.

Updated May 9, 2026
One-click install
npx skills add https://github.com/Immac/pi-extension-creator --skill zero-to-documented-immac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zero-to-documented
Source: https://github.com/Immac/pi-extension-creator/tree/main/skills/zero-to-documented
Command: npx skills add https://github.com/Immac/pi-extension-creator --skill zero-to-documented-immac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a pi extension from scratch involves many disconnected steps—planning the architecture, scaffolding the package, writing TypeScript code, generating documentation, validating the build, and installing it. This Skill orchestrates that entire lifecycle into a single guided workflow so nothing is missed. ## Core Features & Use Cases - End-to-End Workflow: Guides the AI through seven phases—plan, scaffold, implement, document, validate, review, and install—using the extension_creator tool. - Documentation Generation: Produces README.md and ARCHITECTURE.md files with badges, feature lists, and usage sections based on actual source code analysis. - Validation & Review: Runs TypeScript compilation checks and structural reviews before installation to catch manifest and entrypoint errors. - Use Case: A user says "create an extension that blocks dangerous file writes" and the Skill walks through planning the extension type, scaffolding the package, implementing the tool registration, writing docs, validating, and installing to ~/.pi-extensions/. ## Quick Start Ask the AI to create a pi extension for your goal, for example: build an extension that adds a custom tool for git operations.

Frequently Asked Questions about zero-to-documented

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

FAQPage Schema
How do I create a pi extension from scratch?▼

Follow the seven-phase workflow: plan the extension with the extension_creator tool, scaffold the package structure, implement the TypeScript entrypoint, generate documentation, validate the build, review the structure, and optionally install it to ~/.pi-extensions/.

What types of pi extensions can I build?▼

The workflow supports four extension kinds: tool extensions that register custom tools, command extensions that add slash commands, prompt extensions that inject system guidance, and provider extensions. The plan phase infers the appropriate type from your stated goal.

How do I validate a pi extension before installing it?▼

Call the extension_creator tool with mode set to validate and the workspace path. It checks the package manifest, entrypoint configuration, and TypeScript compilation in one pass, returning a status of pass, warn, or fail with diagnostics.

Does the pi extension workflow generate documentation automatically?▼

The document mode provides guidance, but the AI writes the actual README.md and ARCHITECTURE.md by reading the source code. Documentation includes flat-square badges, feature lists, quick start instructions, and usage examples.

Where are pi extensions installed after building?▼

Extensions are installed to ~/.pi-extensions/<name> using a deterministic file copy, and the installation updates ~/.pi/agent/settings.json. Existing installations with the same name are replaced automatically.