the01geek

the01geek/prflow

Use when asked to challenge, refute, push back on, or stress-test an idea, feature request, bug report, GitHub issue, approach, or...

Permanent alias for /prflow:spec, which runs the same issue-drafting pipeline; prefer /prflow:spec. Use when a rough user story, b...

the01geek/prflow

the01geek/prflow

Use when a codebase has no structured developer documentation yet and needs it built from scratch — "we have no docs at all", "set...

the01geek/prflow

Use when customer-facing or public documentation needs to catch up with internal docs or shipped changes — "our public docs still ...

Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the a...

Use when the user asks whether the docs for one topic, feature, or subsystem are accurate — "is the auth flow documented?", "are t...

PRFlow's code-review reception skill (formerly receiving-code-review). Use when addressing review feedback already posted on a pul...

the01geek/prflow

Use when setting up PRFlow in a repo for the first time, or after a plugin update — scaffolds .prflow/config.json from the shipped...

the01geek/prflow

the01geek/prflow

the01geek/prflow

Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles...

the01geek/prflow

Use when the user wants problems in a pull request or the current branch both found AND corrected — "review my changes and fix wha...

Turn a rough request into an implementable GitHub issue through bounded clarification and design decisions — "file a ticket", "ope...

the01geek/prflow