project-workflow

Project lifecycle automation coordinates planning, exploration, feature integration, and release checks through seven integrated slash commands. It generates handoff-ready documentation (PROJECT_BRIEF.md, IMPLEMENTATION_PHASES.md, SESSION.md) and enforces git checkpoints throughout the workflow, eliminating manual coordination steps.

Project workflow automation generates and maintains PROJECT_BRIEF.md, IMPLEMENTATION_PHASES.md, SESSION.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, and ARCHITECTURE.md. These documents preserve context-safe workflows and serve as handoff-ready artifacts for ongoing project management.

Yes. Project workflow automation applies to both new and ongoing projects, executing pre-planning exploration and session management on existing codebases. It coordinates git integration and risk-managed workflows without requiring project restructuring.

Project automation enforces git checkpoints throughout the lifecycle and coordinates git integration into planning, feature implementation, and release-safety checks. It manages context-safe workflows while maintaining version control discipline across project phases.

Project workflow automation coordinates seven integrated slash commands for planning exploration, project planning, feature integration, session management, and release safety checks. Run /plan-project to start; commands generate and maintain lifecycle documentation automatically.

Automated project workflow eliminates manual document creation and coordination by generating PROJECT_BRIEF.md, implementation phases, and session records automatically. It enforces consistent git checkpoints and release-safety validation, reducing context loss and coordination overhead across project phases.