Implements a research-heavy, plan-driven development workflow to ensure code quality before implementation.
Install
mkdir -p .claude/skills/boris-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11297" && unzip -o skill.zip -d .claude/skills/boris-workflow && rm skill.zipInstalls to .claude/skills/boris-workflow
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Conduct deep codebase research
- →Create structured plan documents
- →Execute annotation loops for plan refinement
- →Implement features via checkbox task lists
- →Use red/green TDD during implementation
How it works
The workflow forces a strict sequence of research, planning, and annotation before any implementation code is written.
Inputs & outputs
When to use boris-workflow
- →Plan a new software feature
- →Research a complex codebase bug
- →Document project milestones
About this skill
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:
/boris-start <task>/boris-research [scope]/boris-plan [goal]/boris-review-loop [extra guidance]/boris-open-plan/boris-todos/boris-implement/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:
docs/features/<date>-<slug>/docs/bugs/<date>-<slug>/docs/refactors/<date>-<slug>/docs/migrations/<date>-<slug>/docs/spikes/<date>-<slug>/
Each folder contains:
research.mdplan.md
Phase mapping
1. Research
Kick off deep codebase study and write findings to the work item's research.md.
2. Planning
Use research.md plus fresh source reads to produce plan.md.
The extension can auto-open the current plan.md in the external editor.
3. Annotation loop
After the user edits plan.md, run another /boris-review-loop cycle.
Repeat until the user explicitly approves the plan.
4. Todo breakdown
Before implementation, make sure plan.md has a detailed checkbox task list.
Implementation should not start until this exists.
5. Implementation
Only after approval, execute the plan and mark tasks complete in plan.md.
Use red/green TDD whenever a test harness exists: write or update the test first, run it and observe the failure, then implement the minimum code and rerun until it passes.
If commands are unavailable
Fall back to the prompt templates:
/boris-research-prompt/boris-plan-prompt/boris-annotate-prompt/boris-todos-prompt/boris-implement-prompt
When not to use it
- →When the task is trivial and does not require a formal plan
- →When the user needs immediate code changes without research
Prerequisites
Limitations
- →Requires the user to review and approve the plan document
- →Restricts implementation until the plan is finalized
How it compares
It prevents premature coding by requiring user approval of a detailed plan document before any implementation begins.
Compared to similar skills
boris-workflow side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| boris-workflow (this skill) | 0 | 4mo | No flags | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| writing-plans | 15 | 3mo | Review | Intermediate |
| feature-design-assistant | 6 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by subsy
View all by subsy →You might also like
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
writing-plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
feature-design-assistant
davila7
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
task-coordination-strategies
wshobson
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
avoid-feature-creep
waynesutton
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.
swarm-planner
am-will
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.