psi

A documentation-first workflow aligns software planning with code changes by generating project specifications from docs and READMEs before implementation. This approach keeps artifacts in sync and uses ephemeral planning to enable iterative refinement.

You can generate implementation steps by running a plan-spec-implement cycle that reads project docs, READMEs, and AGENTS.md to auto-extract specifications. The agent then translates these specs into actionable coding tasks.

Yes, the workflow extracts specifications from existing project documentation like READMEs and AGENTS.md. Without these source files, the agent cannot generate accurate specs or align implementation with project plans.

The best way to keep docs in sync with code is using a continuous review process that updates project documentation during implementation. This ensures alignment between specs, plans, and code changes throughout development.

Ephemeral development plans are stored in the ~/.dot-agent directory. This local storage safeguards planning ideas and enables iterative refinement without affecting the main project repository.

Yes, the plan-spec-implement workflow operates without external dependencies. It coordinates planning, specification generation, and implementation steps using only local project docs and ephemeral artifacts.