boris-workflow

name	boris-workflow
description	Use Boris Tane's research -> plan -> annotate -> implement workflow in pi. Use when the user wants a written research document, a reviewed plan document, annotation loops, and no code until the plan is approved.

Boris Workflow

Use this workflow when the user wants the exact "read deeply, write a plan, annotate the plan, then implement" process.

Rules

• Never implement non-trivial work before the user has reviewed and approved the plan document.
• Keep everything grounded in the actual codebase.
• Use persistent markdown artifacts, not chat-only summaries.
• Keep each work item in its own feature-specific folder under docs/.
• Stay in one long session unless the user explicitly asks to split or restart.
• During implementation, keep progress in the plan document via checkbox task lists.

Preferred pi commands

If the package is installed, prefer these commands:

1. /boris-start <task>
2. /boris-research [scope]
3. /boris-plan [goal]
4. /boris-review-loop [extra guidance]
5. /boris-open-plan
6. /boris-todos
7. /boris-implement
8. /boris-status

/boris-start also supports category overrides:

• --feature
• --bug
• --refactor
• --migration
• --spike

Docs structure

The extension keeps each work item in a dedicated folder like: