psi

To keep documentation in sync during feature delivery, you can use a documentation-first workflow that coordinates planning, specification, and implementation. This ensures docs like READMEs and AGENTS.md are continuously updated as development progresses through test-first implementation and CI verification.

A documentation-first workflow for feature delivery coordinates planning, specification, and implementation by applying docs-based specifications to guide code changes. It requires generating temporary plans, writing specs into docs, and verifying implementations via test-first CI checks.

You plan and specify a feature before writing code by generating temporary, ephemeral plan files and research artifacts without committing them to the codebase. You then create docs-based specifications in READMEs, AGENTS.md, and docs/ to guide the subsequent test-first implementation.

Yes, you can use ephemeral planning files without committing them to the codebase. The planning phase generates temporary plan.md files and research artifacts specifically designed to exist outside the codebase while driving the creation of permanent documentation specifications.

Yes, test-first implementation works directly with continuous integration checks. The workflow supports writing tests prior to code implementation and relies on CI verification to ensure the feature delivery meets the specifications defined in the documentation.

The best way to document an authentication flow during development is using a coordinated approach that drafts a temporary plan, writes permanent specifications into AGENTS.md and docs/, implements the code with tests, and continuously updates the documentation as the flow evolves.