home / skills / jezweb / claude-skills / project-workflow

project-workflow skill

safe

/skills/project-workflow

This skill streamlines project lifecycles by orchestrating idea validation, planning, execution, session management, and release across Claude Code workflows.

npx playbooks add skill jezweb/claude-skills --skill project-workflow

Review the files below or copy the command above to add this skill to your agents.

Files (12)

SKILL.md

8.3 KB

---
name: project-workflow
description: |
  Nine integrated slash commands for complete project lifecycle: /explore-idea, /plan-project, /plan-feature, /wrap-session, /continue-session, /workflow, /release, /brief, /reflect.

  Use when starting projects, managing sessions across context windows, capturing learnings, or preparing releases. Saves 35-55 minutes per lifecycle.
user-invocable: true
---

# 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@jezweb-skills`

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

## The 9 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 9 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

Overview

This skill provides nine integrated slash commands to automate a full project lifecycle: idea exploration, planning, session management, context preservation, release checks, and reflection. It streamlines repetitive tasks and preserves context across sessions to save approximately 35–55 minutes per lifecycle. Designed for Claude Code CLI workflows and TypeScript full-stack projects, it fits into Git-based development with optional GitHub publishing.

How this skill works

Each command performs a focused automation step and updates project artifacts (SESSION.md, IMPLEMENTATION_PHASES.md, PROJECT_BRIEF.md, docs/brief-[slug].md). Task and explore agents run analyses that produce structured outputs, git checkpoints, and handoff summaries. Release and reflection commands run safety scans, documentation checks, and route learnings into docs or automation suggestions.

When to use it

When you have a rough idea and need validation or scope decisions (/explore-idea).
When starting a new project or generating planning docs (/plan-project).
When adding a feature to an existing project with session and phase files (/plan-feature).
At the end of a work session or when context is full to checkpoint progress (/wrap-session).
When starting a new session to load context and continue work (/continue-session).
Before publishing to run safety checks and prepare a release (/release).

Best practices

Run /explore-idea before /plan-project if requirements are fuzzy to capture validated decisions.
Keep SESSION.md and IMPLEMENTATION_PHASES.md under version control and run /wrap-session frequently to preserve context.
Use /brief before clearing chat context to generate a portable brief file for future sessions.
Invoke /reflect periodically to capture operational learnings and identify automation candidates.
Run /release only when the repo has commits, package.json (for Node.js), and a configured remote to avoid false checks.

Example use cases

Kick off a new React + Cloudflare project: /explore-idea → /plan-project → work → /wrap-session.
Add a complex feature mid-cycle: /continue-session → /plan-feature → integrate new phases into IMPLEMENTATION_PHASES.md.
Prepare a public release: /wrap-session → /release to run secret scans, docs checks, and optional GitHub tagging.
Preserve context before clearing the chat: /brief to generate docs/brief-[slug].md and optional GitHub issue.
Capture team learnings after a milestone: /reflect to extract patterns, convert rules to CLAUDE.md, and recommend scripts or agents.

FAQ

What files does the skill create or update?

Common outputs include PROJECT_BRIEF.md, IMPLEMENTATION_PHASES.md, SESSION.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, and docs/brief-[slug].md.

Do I need any prerequisites to run commands?

Yes—Claude Code CLI and a git repository are required. /release also expects package.json and a remote for publishing.

How often should I run /wrap-session and /reflect?

Run /wrap-session at each session end or when context nears limits. Run /reflect after major milestones or when learnings accumulate to capture operational knowledge.