agentleFS
ric03uecric03uec/clawrium/.claude/skills/itx-issue-new/SKILL.md

itx-issue-new

Skill67 starsChanged 2 months agoApache-2.0View on GitHub

Create a feature or improvement issue

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a GitHub issue for a feature request or improvement.

    line 9
  2. Distinctive:

    Ask for Customer Outcome: Use the harness's user-question facility to ask:

    line 19
  3. Distinctive:

    Form Issue Title: Use the customer outcome as the issue title.

    line 27
  4. Distinctive:

    If the user provided a description argument, use it for context

    line 33
  5. Very specific:

    Create Issue: Use gh issue create with:

    line 37
  6. Distinctive:

    Always ask for customer outcome before creating the issue

    line 83
  7. Distinctive:

    Do not add labels by default (let triage decide)

    line 85
  8. Very specific:

    REQUIRED: After creating the issue, append prompt log to .itx/<N>/00_PLAN.md.

    line 91

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Issue Creation

Create a GitHub issue for a feature request or improvement.

Instructions

  1. Analyze Context: Review the current conversation for:
    • Feature requests
    • Enhancement ideas
    • Improvement suggestions
    • User pain points
  2. Ask for Customer Outcome: Use the harness's user-question facility to ask:

    "What should the user be able to do when this is implemented?"

    Example outcomes:

    • "User can deploy multiple components in a single command"
    • "User can see resource usage across all services"
    • "User can backup configurations automatically"
  3. Form Issue Title: Use the customer outcome as the issue title.
    • Format: <outcome> (what the user can do after implementation)
    • Example: "User can deploy multiple components in a single command"
    • The user can change this later if needed
  4. Gather Details:
    • If the user provided a description argument, use it for context
    • Identify the problem being solved
    • Note any constraints or preferences
  5. Create Issue: Use gh issue create with:
    gh issue create \
      --title "<customer outcome from step 3>" \
      --body "<structured issue>"
  6. Issue Body Format:

    ## Customer Outcome
    <The outcome statement - what user can do when implemented>
    
    ## Summary
    <What is being proposed>
    
    ## Motivation
    <Why this is needed / what problem it solves>
    
    ## Proposed Solution
    <High-level approach if known>
    
    ## Acceptance Criteria
    - [ ] <criterion 1>
    - [ ] <criterion 2>
    
    ---
    
    <details>
    <summary>Prompt Log</summary>
    
    **Stage**: issue-creation
    **Skill**: /itx-issue-new
    **Timestamp**: <ISO timestamp>
    **Model**: <model>
    
    ```prompt
    <original user prompt/context that led to this issue>
    </details> ```
  7. Return: The issue URL and number

Notes

  • Always ask for customer outcome before creating the issue
  • The outcome becomes the title - focus on what the user gains
  • Do not add labels by default (let triage decide)
  • Focus on the problem/need, not just the solution
  • Include acceptance criteria when possible

Prompt Logging

REQUIRED: After creating the issue, append prompt log to .itx/<N>/00_PLAN.md.

See AGENTS.md for format specification.

mkdir -p .itx/<issue-number>
# Append prompt log to .itx/<issue-number>/00_PLAN.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.