---

name: workflow-status description: "Display project workflow progress by reading handoff documents in .docs/ directory. This skill should be used when users want to check their workflow status, see what phase they're in, or when other workflow skills need to verify prerequisites. Provides reusable prerequisite-checking templates for integration with other workflow skills."

workflow-status

---

If missing PROJECT-MODE.md or brief: -> "Complete project brief with project-brief-writer skill"

If missing tech-stack-decision.md: -> "Select technology stack with tech-stack-advisor skill"

If missing deployment-strategy.md: -> "Define deployment approach with deployment-advisor skill"

If missing project foundation: -> "Generate project foundation with project-spinup skill"

If project foundation complete AND deployment indicates localhost: -> "TERMINATION POINT: Workflow complete for localhost project" -> "Optional: Continue to test-orchestrator when ready for testing infrastructure"

If project foundation complete AND deployment indicates public: -> "Ready to build features! When ready to deploy:" -> " - Use test-orchestrator skill to set up testing (optional)" -> " - Use deploy-guide skill to deploy your application"

If deployment-log.md exists AND no CI/CD: -> "TERMINATION POINT: Manual deployment complete" -> "Optional: Use ci-cd-implement skill to automate deployments"

If CI/CD exists: -> "WORKFLOW COMPLETE: Full automation configured"

After Phase 3 (project-spinup): "Your project foundation is ready. You can:

1. Start development (this is a natural stopping point for localhost/learning projects)
2. Continue workflow when ready to deploy publicly"

After Phase 5 (deploy-guide): "Your application is deployed. You can:

1. Stop here (manual deployment workflow established)
2. Use ci-cd-implement to automate future deployments"

After Phase 6 (ci-cd-implement): "Workflow complete! Your project has full CI/CD automation."

Project: [{project-name}] Mode: {LEARNING|BALANCED|DELIVERY} Current Phase: {phase-number}: {phase-name}

---

Phase Progress

{phase-status-list}

---

Termination Points

{termination-status}

---

Next Step

{next-step-recommendation}

---

Handoff Documents

{document-list}

---

Tip: Any skill can be invoked standalone. Missing prerequisites will be gathered conversationally.

PLANNING PHASES:

• Phase 0: Project Brief
• Phase 1: Tech Stack Selection
• Phase 2: Deployment Strategy

SETUP PHASE:

• Phase 3: Project Foundation <- TERMINATION POINT (localhost)

QUALITY PHASE:

• Phase 4: Test Strategy (optional)

RELEASE PHASES:

• Phase 5: Deployment <- TERMINATION POINT (manual deploy)
• Phase 6: CI/CD <- TERMINATION POINT (full automation)

Status indicators:

• COMPLETE with key details
• [>] IN PROGRESS
• PENDING or AVAILABLE

If at Phase 3 with localhost: "CURRENT TERMINATION: Localhost project - workflow complete for local development"

If at Phase 3 with public deployment planned: "NEXT TERMINATION: After deploy-guide (Phase 5) for manual deployment"

If at Phase 5: "CURRENT TERMINATION: Manual deployment - workflow complete if no CI/CD needed"

If at Phase 6: "WORKFLOW COMPLETE: Full automation configured"

No Workflow Detected

No workflow detected in current directory.

To start a new project workflow:

1. Create or navigate to your project directory
2. Say: "Use project-brief-writer skill"

This will establish your project brief and workflow mode.

Note: Skills can also be used standalone without the full workflow.

---

Then proceed with the skill's main workflow.

{Targeted questions to get equivalent information}

Got it. Let's proceed with {current-phase-action}."

Then proceed with the skill's main workflow.

---

---

workflow-status should clearly indicate which termination point applies.