Riper Workflow

RIPER methodology — Research, Innovate, Plan, Execute, Review. Five-phase systematic development with separation of concerns, persistent artifacts per phase, and approval gates. Use for architecture changes, multi-file refactors, migrations, or any work where mistakes compound.

hermeticormus 3ab8a18 1.2 KB Updated

File contents

RIPER workflow

Phases

  1. Research — read-only. Output: research-notes.md.
  2. Innovate — read-only. Output: approaches.md (2-3 viable).
  3. Plan — write to docs. Output: [task]-plan.md with measurable success criteria.
  4. Execute — full access. Follow plan, verify each step.
  5. Review — read-only after. Output: review.md.

Principles

  • Separation of concerns: each phase has its own access mode
  • Context efficiency: minimal tokens per phase
  • Persistent knowledge: ~/dev/[task]/ per task
  • Conscious transitions: deliberate phase changes

When

Use for architecture, migrations, auth/payments/data work, multi-file refactors.

Don't use for typo fixes, obvious single-file bugs, prototype exploration.


Full content + worked task example at https://github.com/HermeticOrmus/riper-workflow-skills.

hermeticormus/riper-workflow-skills/tree/main/skills/riper-workflow commit 3ab8a189cc

Frequently asked questions

npx skillmds@latest add hermeticormus/riper-workflow