dot-ai-process-feature-request
Skill336 starsChanged 10 months agoMITView on GitHub
Process a feature request or response from another dot-ai project. Reads from tmp directory, implements/integrates, and writes response if needed.
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-prd-update-progressSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- publish-mock-serverSkill
- write-docsSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read and process a feature request or response from another dot-ai project.
- Very specific: line 13
Check for tmp/feature-request.md (incoming request from another project)
- Very specific: line 14
If not found, check for tmp/feature-response.md (response to a request we made)
- Distinctive: line 15
If neither exists, tell the user there's nothing pending
- Distinctive: line 20
Write a response file to the requesting project (path specified in the request)
- Distinctive: line 21
Delete the feature-request.md file: after implementation is complete
- Distinctive: line 24
Read and present the response
- Distinctive: line 25
Use the information to continue integrating the feature
- Distinctive: line 26
Delete the feature-response.md file: after integration is complete
- Distinctive: line 52
Read and understand the full request/response before proceeding
- Distinctive: line 54
Write clear documentation in responses so the requesting project can integrate easily
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Process Feature Request/Response
Read and process a feature request or response from another dot-ai project.
Process
- Check for
tmp/feature-request.md(incoming request from another project) - If not found, check for
tmp/feature-response.md(response to a request we made) - If neither exists, tell the user there's nothing pending
For Incoming Request (feature-request.md)
- Present the request to the user and confirm they want to proceed
- Implement the requested feature
- Write a response file to the requesting project (path specified in the request)
- Delete the feature-request.md file after implementation is complete
For Response (feature-response.md)
- Read and present the response
- Use the information to continue integrating the feature
- Delete the feature-response.md file after integration is complete
Response File Format (for incoming requests only)
# Feature Response from [THIS_PROJECT]
## What Was Implemented
[Brief description of what was built]
## How to Use It
[API signatures, endpoints, types, parameters]
## Examples
[Code examples showing how to call/use the feature]
## Notes
[Any caveats, limitations, or additional context]Guidelines
- Read and understand the full request/response before proceeding
- For requests: use your judgment on the best approach
- Write clear documentation in responses so the requesting project can integrate easily
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

