AI-Assisted Workflows
Projects created from the PearDrop Minimal template include reusable prompt files in .github/prompts/ so GitHub Copilot can follow PearDrop-specific workflows instead of generic scaffolding patterns.
Built-In Prompts
/peardrop-review-spec
Use this when you have a draft feature spec and want Copilot to identify ambiguities, insert clarifications, and capture unanswered questions directly in the spec.
/peardrop-tasks-from-spec
Use this after review to turn the spec into an ordered implementation checklist with explicit testing tasks.
/peardrop-validate-spec
Use this as a final quality gate before implementation. It checks for blockers, missing steps, PearDrop convention drift, and task coverage gaps.
/peardrop-implement-spec
Use this to implement a validated spec one task group at a time. The prompt enforces verification before tasks are marked complete.
/peardrop-cli-workflow
Use this when you want Copilot to plan or execute PearDrop CLI commands safely. It is especially useful for module lifecycle commands, upgrades, scaffolding flows, and migration-related command sequences.
Recommended Flow
1. /peardrop-review-spec
2. /peardrop-tasks-from-spec
3. /peardrop-validate-spec
4. /peardrop-implement-spec
Use /peardrop-cli-workflow whenever the task is primarily a CLI orchestration problem rather than a code-design problem.
Why This Helps
- Keeps Copilot aligned with PearDrop conventions
- Reduces missed steps around projections, read models, migrations, and registration
- Makes testing and verification explicit
- Avoids unsafe CLI usage for rename/remove/update operations
Where These Prompts Live
Generated projects include:
.github/prompts/
peardrop-review-spec.prompt.md
peardrop-tasks-from-spec.prompt.md
peardrop-validate-spec.prompt.md
peardrop-implement-spec.prompt.md
peardrop-cli-workflow.prompt.md
You can customize these prompt files inside your project if your team wants stricter review rules, extra validation gates, or organization-specific workflows.