vibeflow

Orchestrate Claude project workflows with shared .claude state files and slash commands.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/StephenTownsend1234/vibeflow --skill vibeflow-stephentownsend1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeflow
Source: https://github.com/StephenTownsend1234/vibeflow/tree/main
Command: npx skills add https://github.com/StephenTownsend1234/vibeflow --skill vibeflow-stephentownsend1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

vibeflow solves the problem of losing project context between Claude sessions by giving projects a shared workflow for planning, building, and saving progress in a way that compounds over time.

Core Features & Use Cases

  • Session-aware project workflow: use the command suite to orient, plan, execute, and wrap up work without starting from scratch every time.
  • Shared project state: keep decisions, roadmap items, architecture notes, and session progress in a project-owned .claude folder.
  • Collaborative build loop: support iterative software work with bootstrap setup, sprint planning, guarded implementation, and end-of-session capture.
  • Example use case: a founder building with Claude can keep each session aligned to the same goal, the same priorities, and the same project memory.

Quick Start

Tell Claude to use vibeflow to set up your project workflow and then follow the bootstrap, start, build, wrap, and roadmap loop.

Frequently Asked Questions about vibeflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain Claude session continuity for a software project?

Maintain Claude session continuity by orchestrating a shared workflow that saves project state, decisions, and progress in a `.claude` folder, allowing iterative building to compound across sessions without starting from scratch.

What is the best way to keep a Claude roadmap aligned across multiple sessions?

Keep a Claude roadmap aligned across sessions by using coordinated slash-commands for bootstrap, start, build, wrap, and roadmap behavior, which capture progress and update shared project memory at the end of each work loop.

How do I set up sprint planning with Claude for iterative development?

Set up sprint planning with Claude by bootstrapping a project workflow that establishes shared state files, then use the start command to orient each session to current priorities and the build command for guarded implementation.

Do I need a specific repository structure to use shared Claude project state?

You need a repository that supports a project-owned `.claude` folder for shared state files, enabling architecture notes, roadmap items, and session progress to persist directly within your codebase.

Why does Claude lose project context between sessions and how do I fix it?

Claude loses project context between sessions because it lacks persistent memory; fix this by applying a session continuity workflow that wraps up work and captures decisions into shared state files at the end of every session.