Feature Request: Predefined Prompts/workflow templates or MCP prompts for Claude sessions
Summary
Add support for predefined prompts/workflow-templates/plans or even MCP prompts to automate common development tasks, which would have predictable patterns or steps (ex, bugs fixing, adding new feature like api endpoint, tests and etc), so we could maintain very strict set of rules and enforce certain best practices to be followed.
Problem
Currently, Claude code session require detailed prompts for every tasks even when following predictable patterns. While CLAUDE.md file provides project-specific instructions but it is not possible to have reusable plans or steps for different type of tasks.
Proposed Solution
Introduce a predefined prompts/workflow-template to be used by Claude code session:
- Allow projects have predefined steps for common development tasks
- If user starts the session with a template/prompt then after the initial user message, the session would go thru the predefined steps and execute one by one
- So each step can completed properly based on definition before moving into next step
Use Case Examples
Assuming these steps are using MCP servers to interact with solutions like Linear and etc. And these example are here to demonstrate the workflow/steps, but the actual predefined steps/workflow-template can be more descriptive.
Bug Fix Plan:
- Create ticket based on bug description
- Check out a new GitHub branch
- Diagnose and fix the code issue
- Tests
- Commit changes
Feature Addition Plan:
- Create a ticket for the new feature
- Check out a new GitHub branch
- Coding and testing
- Commit changes
Current Workaround
We've created scripts to build prompt and spawn Claude Code with it.
Benefits
- Reduces repetitive prompt engineering
- Automate the tasks
- Increases consistency in development processes
- Can enforce security measures
- Speeds up routine development tasks
- Improves developer experience with Claude Code
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗