mit einem Klick
request-dot-ai-feature
// Generate a feature request prompt for another dot-ai project. Use when you need a feature implemented in a sibling project (MCP server, controller, etc.) to unblock work in the current project.
// Generate a feature request prompt for another dot-ai project. Use when you need a feature implemented in a sibling project (MCP server, controller, etc.) to unblock work in the current project.
Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.
Create changelog fragment for release notes. Invoke during /prd-done workflow during the first push to the PR.
Process a feature request or response from another dot-ai project. Reads from tmp directory, implements/integrates, and writes response if needed.
Query sibling dot-ai projects to verify features are USABLE (not just defined). IMPORTANT: When calling this skill, explain HOW you plan to use the feature (e.g., 'I need to call X via REST API from the UI' or 'I need to import Y function'). This helps verify the full chain from definition to exposure.
Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.
| name | request-dot-ai-feature |
| description | Generate a feature request prompt for another dot-ai project. Use when you need a feature implemented in a sibling project (MCP server, controller, etc.) to unblock work in the current project. |
| allowed-tools | ["Read","Grep","Glob"] |
Write a feature request to a file in the target dot-ai project's tmp directory. The user will review and approve the write operation.
| Project | Directory | Description |
|---|---|---|
| dot-ai | ../dot-ai | Main MCP server (API endpoints, tools, handlers) |
| dot-ai-ui | ../dot-ai-ui | Web UI for visualizations and dashboard |
| dot-ai-controller | ../dot-ai-controller | Kubernetes controller |
| dot-ai-stack | ../dot-ai-stack | Stack deployment configs |
| dot-ai-website | ../dot-ai-website | Documentation website |
Important: Do NOT use this skill to request features in the project you're currently working in. Just implement them directly.
basename $(git rev-parse --show-toplevel)../[target-project]/tmp/feature-request.md/process-feature-requestWrite the feature request file with this content (replace [CURRENT_PROJECT] with the actual project name from step 2):
# Feature Request from [CURRENT_PROJECT]
**Requesting project directory:** ../[CURRENT_PROJECT]
## What We Need
[DESCRIPTION OF WHAT WE NEED AND WHY]
## Our Suggestion
(You decide the best approach)
- [Suggested approach or implementation idea]
## Context
[What this unblocks in our project]
## Notes
You're the expert on this codebase. Feel free to implement this differently if there's a better approach, or push back if this doesn't make sense.
## Response Instructions
After implementing this feature, write a response file to help the requesting project integrate:
1. Write to: `../[CURRENT_PROJECT]/tmp/feature-response.md`
2. Include: what was implemented, how to use it (API signatures, endpoints, types), and any usage examples