air-workflow

Model project work as files with lifecycle states in Air documents.

27|4|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/rytswd/pi-agent-extensions --skill air-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: air-workflow
Source: https://github.com/rytswd/pi-agent-extensions/tree/main/air
Command: npx skills add https://github.com/rytswd/pi-agent-extensions --skill air-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Air provides a filesystem-based workflow to plan, document, and track project work by modeling artifacts as files and explicit lifecycle states.

Core Features & Use Cases

  • Documentation-driven planning: plan features, requirements, and tasks directly within Air documents and folders.
  • State-based lifecycle: manage draft, ready, work-in-progress, complete, and archived states with clear transitions.
  • Git-aware collaboration: keep documentation aligned with version control and history for auditable progress.
  • Context-driven automation: generate AI context and operational instructions from Air documents to support automation and reviews.
  • Use Case: coordinate specifications to implementation across teams by aligning documents, tags, and statuses in a single repository.

Quick Start

Create an Air document in v0.1/ with state draft, then progressively move it to ready as the plan is finalized.

Frequently Asked Questions about air-workflow

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

FAQPage Schema
How do I manage project documentation with explicit lifecycle states?

Model project artifacts as files with explicit lifecycle states like draft, ready, work-in-progress, complete, and archived. This filesystem-driven approach tracks progress and aligns specifications directly within your repository folders.

What is documentation-driven planning for project tracking?

Documentation-driven planning uses filesystem-based documents to plan features, requirements, and tasks. It models work as files and states to drive project tracking and collaboration, allowing teams to coordinate specifications through version-controlled folders.

How do I start tracking specifications using a filesystem-based workflow?

Create an Air document in a v0.1/ folder with the state draft, then progressively move it to ready as the plan finalizes. Define a context-generation process with a SKILL.md frontmatter to manage transitions.

Can I keep documentation aligned with version control history?

Yes, you can keep documentation aligned with version control for auditable progress. This git-aware collaboration ensures your filesystem-modeled artifacts and state transitions remain synchronized with repository history.

Does state-based project management work for coordinating across teams?

State-based project management coordinates specifications to implementation across teams by aligning documents, tags, and statuses in a single repository. It generates AI context and operational instructions to support automation and reviews.

Do I need a SKILL.md frontmatter to use filesystem-driven workflow documents?

Yes, a SKILL.md frontmatter with name and description is required. You can also include optional resources like scripts, references, and assets to support the defined context-generation process.