sherpy-flow
Sherpy Flow
Runs the complete Sherpy planning pipeline from start to finish. Detects your current position in the workflow based on existing artifacts and resumes from there. You never need to remember which skill comes next or what its inputs are.
Usage
/sherpy-flow [output-directory]
If no directory is provided, prompt the user: "Where should I create the planning documents?"
Wait for the user to provide a path before proceeding.
The Pipeline
Step 1 Gap Analysis Worksheet → gap-analysis-worksheet.md
Step 2 Business Requirements → business-requirements.yaml
More from validkeys/sherpy
technical-requirements-interview
Conducts structured interviews to derive technical requirements from business requirements. Requires completed business-requirements.yaml as input. Asks targeted technical questions about architecture, technology stack, data model, APIs, security, testing, and deployment. Generates technical-requirements.yaml output.
52business-requirements-interview
Conducts structured interviews to gather comprehensive business requirements. Asks one question at a time with multiple-choice options, tracks progress in JSONL format, and generates structured business-requirements.yaml output. Use when starting a new project or feature to ensure clear understanding of goals, scope, users, and success criteria.
51implementation-planner
Generates detailed implementation plans with milestones and tasks from business and technical requirements. Embeds best practices including task sizing (30m-2.5h), style anchors, TDD requirements, and quality constraints. Outputs milestones.yaml and milestone-m*.tasks.yaml files ready for development.
44implementation-plan-review
Reviews generated implementation plans against best practices including task sizing (30m-2.5h), style anchors, TDD requirements, drift prevention, and quality constraints. Validates milestones.yaml and task files for completeness, alignment, and development readiness.
41implementation-plan-best-practices
Educational guide on best practices for creating implementation plans that prevent drift. Covers style anchors, task sizing, TDD requirements, affirmative instructions, drift handling, and quality gates. Use when creating or improving implementation plans to ensure they follow proven patterns.
39definition-of-done
Enhances milestones.yaml with detailed acceptance criteria for each milestone. Derives functional acceptance criteria, non-functional gates, testing requirements, documentation requirements, and exit checklists from business and technical requirements. Updates milestones.yaml in place with optional acceptance_criteria and exit_checklist fields.
33