capture-project-intake
Skill0 starsChanged 3 months agoMITView on GitHub
Record a message explicitly framed as a support ticket or feature request in this project's Markdown intake queue. Use when the user says support ticket or feature request, or begins the message with ISSUE, BUG, TASK, or FEATURE. This is capture-only: stop after writing and do not investigate, plan, promote, fix, or implement the item.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- clean-up-worktreeSkill
- coordinate-parallel-workSkill
- deliver-project-workSkill
- develop-projectSkill
- integrate-reviewed-changeSkill
- investigate-projectSkill
- manage-project-workSkill
- map-project-planningSkill
- release-projectSkill
- review-project-changeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use and increment that file's next identifier.
- Distinctive: line 22
Update the queue's date and empty marker as its format requires.
- Distinctive: line 23
Stop after capture. Do not inspect code, investigate, prioritise, plan, promote, fix, or implement in the same turn, even if the intake …
- Distinctive: line 29
Use the exact issue or feature intake shape in the workflow contract.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Capture Project Intake
Execution mode
inline
../../WORKFLOW.md is the canonical lifecycle, identifier,
and record-shape contract. This skill owns capture behavior only.
Record only the request
- Open only
../../ISSUES.mdfor a support ticket, issue, bug, task, maintenance, or security report, or../../FEATURES.mdfor a product idea. - Use and increment that file's next identifier. Preserve every existing item.
- Record only details stated by the user. Do not infer priority, root cause, solution, scope, or acceptance criteria.
- Update the queue's date and empty marker as its format requires.
- Stop after capture. Do not inspect code, investigate, prioritise, plan, promote, fix, or implement in the same turn, even if the intake message asks for implementation.
A later explicit request must select or promote the item before work begins.
Use the exact issue or feature intake shape in the workflow contract.
Confirm the identifier, summary, and queue in the final response. Do not turn capture into triage.
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.