// Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Append a learning to agent-learnings.md when the agent or user identifies a mistake, non-obvious pattern, or useful convention worth remembering. Use when the user says "capture this", "remember this", or "add to learnings".
Set up MSC credentials and MCP server integration for cloud storage access. Use when the user wants to interact with cloud storage (S3, GCS, Azure, OCI), asks to set up credentials, connect to a bucket, list objects, move files, or sync data. Checks for existing config first — only runs interactive setup if credentials are missing.
Fix CVE vulnerabilities by upgrading affected dependencies across Python (uv), Go, and Rust layers. Use when the user mentions CVE numbers, asks to fix security vulnerabilities, or asks to patch dependencies for CVEs.
Produce a test plan with specific test names, assertions, and coverage across Python, Rust, and Go. Use when planning tests for a feature, after generating a spec, or the user asks for a test plan.
Stage files, commit with correct format, push, and generate an MR description. Manual invocation only — has side effects (git operations). Use when the user explicitly asks to prepare, create, or submit an MR.
Prepares and automates the release process for multi-storage-client (version bump, release notes, checklist). Use when the user wants to cut a release, bump version, prepare release, publish a new version, or automate release steps.
| name | generate-spec |
| description | Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out. |
| invocable | auto |
Produce a detailed feature specification before implementation begins. The spec becomes the source of truth for implementation and verification.
Clarify with the user:
Determine:
.pyi stub and Python wrapper updates?Use this template:
## Feature Spec: <title>
### Summary
<1-2 sentence description>
### API Changes
- <new/changed functions, classes, config options with type signatures>
### Backward Compatibility
- <breaking or non-breaking>
- <migration path if breaking>
### Cross-Language Impact
| Layer | Changes Required |
|-------|-----------------|
| Python | … |
| Rust | … |
| Go (FUSE) | … |
| .pyi stubs | … |
### File-Level Change Plan
| File | Change |
|------|--------|
| … | … |
### Performance Considerations
- <expected impact, benchmarks needed>
### Acceptance Criteria
- [ ] <specific, testable criterion>
- [ ] <specific, testable criterion>
Present the spec to the user. Do not proceed to implementation until approved.