Open Source · MIT Licensed · AI-Native
Tried, tested, and battle-scarred. I built PWP after losing enough hair to my chaotic projects that I started budgeting for hats. Consider this my gift to the dev community — so you can ship production-grade software and keep your hairline intact. Whether you're solo, a startup, or an enterprise squad.
> The Problem
Runtime crash in production. Your users find the bug before you do.
Untested code ships. Regression appears 3 sprints later. Nobody knows why.
Hallucinated API calls. Invented dependencies. Security vulnerability deployed.
> The Solution
Written implementation plans before any code is written. Every change is traceable to a business requirement. No more "why does this file exist?"
Branch naming, commit conventions, and code standards enforced through convention — not tooling. Works with any stack, any language.
Pre-merge checklists, post-merge monitoring, visual QA, and performance baselines. Nothing ships without proof it works.
A dedicated skill file that turns your AI copilot into a disciplined junior engineer. No hallucinations. No scope creep. No invented APIs.
Docs are updated in the same PR as the code. Feature traceability, architecture walkthroughs, and changelogs — always current.
Defined procedures for build failures, merge conflicts, and production regressions. No panic, just process.
A structured testing strategy with unit, integration, and E2E coverage. Flaky test quarantine, coverage thresholds, and the testing pyramid — enforced, not optional.
Environment promotion from staging to production with rollback plans, health checks, and feature flags. Zero-surprise releases every time.
Audit schedules, pinned versions, license checks, and lockfile hygiene. No phantom upgrades. No supply-chain surprises.
8 drop-in skill files for common engineering tasks — debugging, code review, security audits, migrations, and more. Plug them into any AI agent.
> For the Vibe Coders
Yes. Especially you.
If you're building with Cursor, Bolt, v0, or ChatGPT — you're already shipping fast. That's not the problem. The problem is what happens after you ship.
There's no config to install. No CLI to learn. No dependencies. It's just markdown files — the same stuff your AI already reads. Drop them into your project folder. Your AI reads the rules. You build better software. That's the whole workflow.
> Built For
You're the PM, dev, and QA. PWP gives you the "senior engineer review" you don't have. Skip what you don't need, enforce what matters.
3–8 people shipping fast. PWP is your async alignment tool — new hires read the protocol and know exactly what's expected. No "unspoken rules."
Security, compliance, long-term maintainability. Every commit traces back to a plan. Every plan traces back to a business requirement.
> Get Started in 5 Minutes
git clone https://github.com/shandar/Project_Workflow_Protocol.git .
Drop the protocol/, templates/, and skills/ folders
into any existing or new project. No dependencies required.
cat skills/ai-agent-protocol.skill.md | pbcopy
Paste the skill into Cursor Rules, Windsurf Settings, Custom GPT instructions, or any LLM system prompt. Your AI now follows your rules.
cp templates/plan-template.md docs/PLAN-001.md
Before writing any implementation, fill out the plan template. Define the problem, list files, set verification steps. Then build.
cat templates/verification-checklist.md
Use the pre-merge checklist on every PR. Type check, build, lint, test. No exceptions.
> Browse the Repository
53 files · 5 directories · Everything you need to ship with discipline
Clone the repo. Drop it in. Start building with discipline.