Back to Workflow & Productivity

project-workflow

project managementautomationsoftware developmentplanningideationfeature developmentproject lifecyclecoding assistant
โญ 860๐Ÿ“„ MIT๐Ÿ•’ 2026-06-11Source โ†—

Install this skill

npx skills add jezweb/claude-skills

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

The project-workflow skill provides a structured suite of nine slash commands that standardize the software development lifecycle within terminal environments. By automating repetitive administrative tasks like session checkpointing, documentation generation, and release compliance, it addresses the common issue of context degradation during extended development sessions. The tool manages project state through persistent files like SESSION.md and IMPLEMENTATION_PHASES.md, ensuring that task status and technical decisions remain traceable across disconnected work sessions. Instead of relying on manual git logs or scattered markdown notes, the skill orchestrates the transition between research, execution, and deployment phases. It is built to keep agents synchronized with the project's evolution, maintaining clear boundaries between planning, active coding, and final quality assurance audits before publishing code to public repositories.

When to Use This Skill

  • โ€ขResuming a complex development project after a multi-day hiatus
  • โ€ขValidating technical feasibility of a feature before writing code
  • โ€ขEnsuring a repository meets quality and security standards before deployment
  • โ€ขOnboarding into a new codebase with pre-established project phases

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

  • โ€œHelp me manage my project flow
  • โ€œHow do I prepare for my next session?
  • โ€œCheck if this code is ready for public release
  • โ€œI need to document my recent project learnings
  • โ€œWhat is the next step for this feature?

Pro Tips

  • ๐Ÿ’กAlways initiate with `/explore-idea` when faced with ambiguous concepts to effectively validate ideas and refine project scope before committing to detailed planning.
  • ๐Ÿ’กLeverage the generated `SESSION.md` and `IMPLEMENTATION_PHASES.md` as living documents. Update them regularly to maintain continuity and context throughout your project's lifecycle.
  • ๐Ÿ’กIntegrate the outputs from planning commands (e.g., `DATABASE_SCHEMA.md`, `API_ENDPOINTS.md`) directly into your version control system to foster team collaboration and maintain a single source of truth.

What this skill does

  • โ€ขAutomates project scaffolding via session and implementation documentation
  • โ€ขPerforms pre-release safety audits including secret scanning and dependency audits
  • โ€ขCaptures session state to facilitate rapid context restoration after breaks
  • โ€ขGenerates structured project briefs to validate concepts before implementation
  • โ€ขRefines project documentation by extracting technical learnings from conversations

When not to use it

  • โœ•During simple, single-file script writing or short-lived experiments
  • โœ•When project requirements are too volatile for rigid phase documentation

Example workflow

  1. /explore-idea to define project scope
  2. /plan-project to build core documentation
  3. Execute development tasks
  4. /wrap-session to commit state and save progress
  5. /continue-session to resume work
  6. /release to verify quality and deploy

Prerequisites

  • โ€“Git version control initialized in the directory
  • โ€“Claude Code or compatible agent environment installed

Pitfalls & limitations

  • !Requires manual maintenance of SESSION.md if files are modified outside the agent
  • !Strict documentation requirements in the /release command may cause friction for small, informal projects
  • !Over-reliance on automated session files can lead to outdated plans if not refreshed regularly

FAQ

Does this replace my manual git commits?
No, it adds a layer of organization on top of git, ensuring your commit messages and checkpoints are tied to the specific project phase.
What happens if I forget to run /wrap-session?
The context might be harder to recover during your next session; you will lose the structured summary that the agent uses to orient itself.
Can I use this for non-coding projects?
While it focuses on technical workflows, the documentation generation and project brief features can be adapted for any task-based project lifecycle.

How it compares

Unlike manual prompt-based planning which often ignores project state persistence, this skill maintains specific tracking files, ensuring the agent remains aligned with current requirements and blockers.

Source & trust

โญ 860 stars๐Ÿ“„ MIT๐Ÿ•’ Updated 2026-06-11
๐Ÿ“„ Full skill instructions โ€” original source: jezweb/claude-skills
# Project Workflow Skill

9 integrated slash commands for complete project lifecycle automation: idea validation โ†’ planning โ†’ execution โ†’ session management โ†’ context preservation โ†’ release.

**Time savings**: 35-55 minutes per project lifecycle

## Installation

**Marketplace**: /plugin install project-workflow@claude-skills

**Manual**: Copy commands/*.md to ~/.claude/commands/

## The 7 Commands

### 1. /explore-idea - Pre-Planning Exploration

**Use when**: Rough idea that needs tech stack validation, scope management, or research before planning.

**Creates**: PROJECT_BRIEF.md with validated decisions โ†’ hands off to /plan-project

**Time savings**: 10-15 min

---

### 2. /plan-project - Generate Project Planning Docs

**Use when**: Starting new project with clear requirements, or after /explore-idea.

**Creates**: IMPLEMENTATION_PHASES.md, SESSION.md, DATABASE_SCHEMA.md (if needed), API_ENDPOINTS.md (if needed), ARCHITECTURE.md

**Invokes**: project-planning skill

**Time savings**: 5-7 min

---

### 3. /plan-feature - Add Features to Existing Projects

**Use when**: Adding feature to existing project with SESSION.md + IMPLEMENTATION_PHASES.md.

**Does**: Generates new phases via project-planning skill, integrates into IMPLEMENTATION_PHASES.md with renumbering, updates SESSION.md.

**Time savings**: 7-10 min

---

### 4. /wrap-session - End-of-Session Checkpoint

**Use when**: Context full (>150k tokens), end of work session, or before task switch.

**Does**: Task agent analyzes session โ†’ updates SESSION.md (progress, Next Action, blockers) โ†’ git checkpoint commit โ†’ formatted handoff summary.

**Time savings**: 2-3 min

---

### 5. /continue-session - Start-of-Session Context Loading

**Use when**: Starting new session or after /wrap-session checkpoint.

**Does**: Explore agent loads SESSION.md + planning docs โ†’ shows git history + session summary (phase, progress, Next Action, blockers) โ†’ optionally opens file โ†’ asks permission to continue.

**Time savings**: 1-2 min

---

### 6. /workflow - Interactive Workflow Guide

**Use when**: First time user, unsure which command to use, or need quick reference.

**Does**: Shows all 7 commands โ†’ context-aware guidance with decision trees โ†’ offers to execute appropriate command.

---

### 7. /release - Pre-Release Safety Checks

**Use when**: Ready to push to public GitHub or create release.

**8 Phases**:
1. **Critical Safety** (BLOCKERS): Secrets scan (gitleaks), personal artifacts check, git remote verification
2. **Documentation** (REQUIRED): LICENSE, README (>100 words), CONTRIBUTING.md (>500 LOC), CODE_OF_CONDUCT (>1000 LOC)
3. **Configuration**: .gitignore, package.json, git branch warning
4. **Quality** (NON-BLOCKING): Build test, npm audit, large files (>1MB)
5. **Report**: Blockers/warnings/recommendations + safe to release verdict
6-8. **Auto-Fix & Publish**: Fix issues, release prep commit, optional git tag + GitHub release

**Time savings**: 10-15 min

---

### 8. /brief - Context Preservation Document

**Use when**: Before clearing context, to preserve key decisions and requirements for future sessions.

**Creates**: docs/brief-[slug].md with extracted information from current conversation.

**Does**: Analyzes conversation โ†’ extracts what's being built, decisions made, technical details โ†’ creates organized markdown file โ†’ optionally creates GitHub issue for tracking.

**Time savings**: 3-5 min

---

### 9. /reflect - Capture Operational Knowledge

**Use when**: Before context compaction, after completing significant work, or when valuable learnings accumulated.

**Does**: Reviews conversation โ†’ identifies workflows discovered, patterns learned, tool sequences, corrections made โ†’ routes each learning to appropriate destination (rules, CLAUDE.md, skills, docs) โ†’ optionally suggests automation (scripts, commands, custom agents).

**Key Feature**: Considers whether processes should become custom agents when they require reasoning/decisions, benefit from parallel execution, or involve research/exploration.

**Time savings**: 5-10 min

---

## Workflow Examples

**Full**: /explore-idea โ†’ /plan-project โ†’ work โ†’ /wrap-session โ†’ /continue-session โ†’ /plan-feature (if needed) โ†’ repeat โ†’ /reflect โ†’ /release

**Quick** (clear requirements): /plan-project โ†’ work โ†’ /wrap-session โ†’ /continue-session โ†’ /release

**Context Preservation**: /brief (before clearing context), /reflect (capture learnings)

**Helpers**: /workflow (guidance), /plan-feature (add feature), /release (publish)

---

## Integration

**project-planning**: Invoked by /plan-project and /plan-feature (generates IMPLEMENTATION_PHASES.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md)

**project-session-management**: SESSION.md protocol for /wrap-session and /continue-session

**Claude Code agents**: /wrap-session (Task agent), /continue-session + /explore-idea (Explore agent)

---

## Command Relationships

EXPLORATION PHASE
/explore-idea (optional)
โ†“
Creates PROJECT_BRIEF.md
โ†“
PLANNING PHASE
/plan-project (reads PROJECT_BRIEF.md if exists)
โ†“
Creates IMPLEMENTATION_PHASES.md + SESSION.md
โ†“
EXECUTION PHASE
Work on phases
โ†“
/wrap-session (when context full)
โ†“
Updates SESSION.md, git checkpoint
โ†“
/continue-session (new session)
โ†“
Loads SESSION.md, continues work
โ†“
/plan-feature (when need new features)
โ†“
Adds phases to IMPLEMENTATION_PHASES.md
โ†“
Continue wrap โ†’ resume cycle
โ†“
CONTEXT PRESERVATION
/brief (before clearing context)
โ†“
Creates docs/brief-[slug].md
โ†“
/reflect (capture learnings)
โ†“
Routes knowledge to rules, docs, CLAUDE.md
โ†“
RELEASE PHASE
/release (when ready to publish)
โ†“
Safety checks โ†’ GitHub release

HELPER
/workflow (anytime)
โ†“
Interactive guidance


---

## Time Savings Breakdown

| Command | Time Saved | Tasks Automated |
|---------|------------|-----------------|
| /explore-idea | 10-15 min | Research, validation, scope management, tech stack evaluation |
| /plan-project | 5-7 min | Planning doc generation, git setup, phase structuring |
| /plan-feature | 7-10 min | Feature planning, phase integration, doc updates |
| /wrap-session | 2-3 min | SESSION.md updates, git checkpoint, handoff summary |
| /continue-session | 1-2 min | Context loading, git history review, next action display |
| /workflow | Instant | Navigation, decision trees, command selection |
| /release | 10-15 min | Secret scanning, doc validation, build testing, release creation |
| /brief | 3-5 min | Context extraction, decisions capture, markdown generation |
| /reflect | 5-10 min | Learning extraction, knowledge routing, automation suggestions |

**Total per project lifecycle:** 45-70 minutes

---

## Prerequisites

**All**: Claude Code CLI, git repo (recommended)

**/plan-feature**: Existing SESSION.md + IMPLEMENTATION_PHASES.md

**/wrap-session, /continue-session**: SESSION.md (created by /plan-project)

**/release**: Git repo with commits, package.json (Node.js), remote URL (for publishing)

---

## Troubleshooting

**/plan-project "No project description"**: Use /explore-idea first or discuss project with Claude

**/plan-feature "Prerequisites not met"**: Run /plan-project first (creates SESSION.md + IMPLEMENTATION_PHASES.md)

**/wrap-session "No git repository"**: Run git init

**/continue-session "SESSION.md not found"**: Run /plan-project

**/release "Secrets detected"**: Add to .gitignore, remove from git history

---

## Version History

**1.1.0** (2026-01-11)
- Added /brief command for context preservation
- Added /reflect command for capturing operational knowledge
- /reflect now suggests custom agents for processes requiring reasoning
- Total commands: 9

**1.0.0** (2025-11-12)
- Initial release
- 7 integrated slash commands
- Plugin marketplace distribution
- Command bundling via plugin.json

---

**Issues**: https://github.com/jezweb/claude-skills/issues | **Author**: Jeremy Dawes ([email protected]) | **License**: MIT

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/project-workflow/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/jezweb/claude-skills/project-workflow/SKILL.md
  • Cursor: ~/.cursor/skills/jezweb/claude-skills/project-workflow/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/jezweb/claude-skills/project-workflow/SKILL.md

๐Ÿš€ Install with CLI:
npx skills add jezweb/claude-skills

Read the Master Guide: Mastering Agent Skills โ†’

Recommended Rules

View more rules โ†’

Recommended Workflows

View more workflows โ†’

Recommended MCP Servers

View more MCP servers โ†’

Take It Further

Maximize your productivity with these powerful resources

๐Ÿ“‹

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
๐Ÿ“–

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid workflow & productivity issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under Workflow & Productivity and is published by JezWeb, maintained in jezweb/claude-skills.

โ† Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.