Structured AI Workflow with Phase-Based Commands to Reduce Rework

A developer on r/ClaudeAI describes a repeatable, programmable workflow designed to address persistent issues when using AI for daily development. The core problem identified was not needing a smarter model, but needing a repeatable process to stop fixing the same mistakes. Key pain points included AI losing context between sessions, breaking project standards on basics like naming and style, mixing planning with execution, and treating documentation as an afterthought.

Phase-Based Command Workflow

The solution replaces reliance on a single giant prompt with a series of clear, phase-specific commands:

• /pwf-brainstorm – Defines scope, architecture, and decisions.
• /pwf-plan – Turns the brainstorm into executable phases and tasks.
• Optional quality gates: /pwf-checklist, /pwf-clarify, /pwf-analyze.
• /pwf-work-plan – Executes the plan phase by phase.
• /pwf-review – Performs a deeper review.
• /pwf-commit-changes – Closes the task with structured commits.

For small tasks, the developer uses /pwf-work but maintains review and documentation discipline.

The Critical Rule

The rule that had the most significant impact on quality: /pwf-work and /pwf-work-plan are required to read documentation before implementation and update it afterward. This ensures the AI works with "project memory" instead of "half blind," dramatically improving consistency and reducing rework.

Supporting Project Structure

The workflow is supported by a specific project structure to improve AI context:

• One folder for code repositories.
• One folder for workspace assets (docs, controls, configs).

Both folders are opened as multi-root in an editor (like VS Code or Cursor), creating a monorepo-like experience that helps the AI see the full system without chaos.

Results and References

The developer reports direct impacts: fewer repeated mistakes, less rework, better consistency across sessions, and more output with fewer errors. They cited closing 25 tasks (small, medium, large) in a day by avoiding the same error loop. The approach was informed by studying concepts like Compound Engineering, Superpowers, Spec Kit, and Spec-Driven Development, but adapted and refined through personal use rather than copying a framework.