explainx.ainewsletter3.4k
Productivity

project-workflow▌

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill project-workflow
0 commentsdiscussion
summary

Nine integrated slash commands automating project lifecycle from idea validation through release.

  • ›Commands span exploration, planning, execution, session management, context preservation, and release phases with 35-55 minutes total time savings per project
  • ›/wrap-session and /continue-session manage context across multiple sessions via SESSION.md checkpoints and git commits
  • ›/release performs eight-phase safety checks including secret scanning, documentation validation, and build testi
skill.md

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

how to use project-workflow

How to use project-workflow on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add project-workflow
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill project-workflow

The skills CLI fetches project-workflow from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/project-workflow

Reload or restart Cursor to activate project-workflow. Access the skill through slash commands (e.g., /project-workflow) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.5★★★★★70 reviews
  • ★★★★★Dhruvi Jain· Dec 24, 2024

    We added project-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Aanya Ramirez· Dec 20, 2024

    We added project-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Olivia Farah· Dec 8, 2024

    Useful defaults in project-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Olivia Khan· Dec 4, 2024

    Keeps context tight: project-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Aditi Rao· Dec 4, 2024

    Solid pick for teams standardizing on skills: project-workflow is focused, and the summary matches what you get after install.

  • ★★★★★Omar Malhotra· Nov 27, 2024

    We added project-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Noah Harris· Nov 23, 2024

    project-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Soo Yang· Nov 23, 2024

    I recommend project-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Oshnikdeep· Nov 15, 2024

    Useful defaults in project-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Luis Martin· Nov 11, 2024

    Useful defaults in project-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 70

1 / 7