Nine integrated slash commands automating project lifecycle from idea validation through release.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproject-workflowExecute the skills CLI command in your project's root directory to begin installation:
Fetches project-workflow from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate project-workflow. Access via /project-workflow in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
697
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
697
stars
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
Marketplace: /plugin install project-workflow@jezweb-skills
Manual: Copy commands/*.md to ~/.claude/commands/
/explore-idea - Pre-Planning ExplorationUse 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
/plan-project - Generate Project Planning DocsUse 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
/plan-feature - Add Features to Existing ProjectsUse 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
/wrap-session - End-of-Session CheckpointUse 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
/continue-session - Start-of-Session Context LoadingUse 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
/workflow - Interactive Workflow GuideUse 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.
/release - Pre-Release Safety ChecksUse when: Ready to push to public GitHub or create release.
8 Phases:
Time savings: 10-15 min
/brief - Context Preservation DocumentUse 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
/reflect - Capture Operational KnowledgeUse 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
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)
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)
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
| 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
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)
/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
1.1.0 (2026-01-11)
/brief command for context preservation/reflect command for capturing operational knowledge/reflect now suggests custom agents for processes requiring reasoning1.0.0 (2025-11-12)
Issues: https://github.com/jezweb/claude-skills/issues | Author: Jeremy Dawes ([email protected]) | License: MIT
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jezweb/claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
We added project-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added project-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in project-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: project-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: project-workflow is focused, and the summary matches what you get after install.
We added project-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
project-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend project-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in project-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
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