Create a new Standard Operating Procedure (SOP) file with proper structure
Creates structured Standard Operating Procedure files with RFC 2119 compliance and validation steps.
/plugin marketplace add TheBushidoCollective/han/plugin install hashi-gitlab@hanhashi-agent-sop:create-sop - Create a new Standard Operating Procedure file
/create-sop
This command guides users through creating well-structured Standard Operating Procedures (SOPs) for AI agents. It provides step-by-step assistance in determining SOP purpose, structuring content, applying RFC 2119 keywords, and saving files with proper naming conventions.
You are helping the user create a new Standard Operating Procedure (SOP) file.
Guide the user through creating a well-structured SOP file by:
Ask about the SOP purpose (if not provided):
Determine SOP type:
Create the SOP file following this structure:
# {Action Verb} {Specific Outcome}
## Overview
{1-2 sentences describing what this SOP accomplishes and when to use it}
## Parameters
- **Parameter Name**: {parameter_name} - Description and example values
- **Configuration**: {config_option} - Available options
## Prerequisites
### Required Tools
- Tool name (version X.X or higher)
### Required Knowledge
- Understanding of relevant concepts
### Required Setup
- Required environment configuration
## Steps
1. First major step
- Sub-step with details
- Another sub-step
- **Validation**: How to verify this step succeeded
2. Second major step
- Implementation detail
- Expected outcome
- **Validation**: Verification method
3. Third major step
- Specific actions
- Success indicators
## Success Criteria
- [ ] Measurable outcome 1
- [ ] Measurable outcome 2
- [ ] Measurable outcome 3
- [ ] All tests pass
- [ ] Documentation updated
## Error Handling
### Error: {Common Error Name}
**Symptoms**: How this error manifests
**Cause**: Why this error occurs
**Resolution**:
1. First troubleshooting step
2. Second troubleshooting step
3. Alternative approach
## Related SOPs
- **{related-sop}**: When to use this instead
- **{complementary-sop}**: What to do next
Use RFC 2119 keywords appropriately:
File naming:
.sop.md extensiondeploy-production.sop.md, code-review-security.sop.mdSave location:
~/sops/ as default)~/sops/deployment/, ~/sops/development/.sop.md extensionUser: "Help me create an SOP for deploying to production"
Response: