~aod-score
Skill95 starsChanged 38 days agoApache-2.0View on GitHub
Re-score an existing idea's ICE rating when circumstances change. Use this skill when you need to re-evaluate ideas, update ICE scores, change idea priority, or re-assess deferred ideas.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ~aod-blueprintSkill
- ~aod-bugfixSkill
- ~aod-buildSkill
- ~aod-defineSkill
- ~aod-deliverSkill
- ~aod-discoverSkill
- aod-foundationSkill
- ~aod-kickstartSkill
- aod-lensSkill
- aod-orchestrateSkill
- ~aod-planSkill
- ~aod-project-planSkill
- ~aod-runSkill
- ~aod-specSkill
- aod-stackSkill
- ~aod-statusSkill
- code-execution-helperSkill
- git-workflow-helperSkill
- kb-createSkill
- kb-querySkill
- root-cause-analyzerSkill
- securitySkill
- tachi-control-analysisSkill
- tachi-infographicsSkill
- tachi-orchestrationSkill
- tachi-report-assemblySkill
- tachi-risk-scoringSkill
- tachi-sharedSkill
- tachi-threat-reportingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 9 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Update an existing idea's ICE (Impact, Confidence, Effort) score when circumstances change, new information emerges, or priorities shift.
- Very specific: line 29
If invalid or missing, display usage: Usage: /aod.score NNN (or #NNN or IDEA-NNN)
- Distinctive: line 33
Search for the matching GitHub Issue:
- Distinctive: line 45
If no issue is found, display an error and exit:
- Very specific: line 52
Read the GitHub Issue body using gh issue view {number} --json body,title.
- Distinctive: line 124
If current status is "Deferred" and new score >= 12: Set status to "Scoring"
- Distinctive: line 125
If current status is "Scoring" and new score < 12: Set status to "Deferred"
- Distinctive: line 126
If current status is "Validated": Preserve status (already PM-approved, do not downgrade)
- Very specific: line 127
If current status is "Rejected" and new score >= 12: Set status to "Scoring" (re-opens for re-validation via /aod.validate)
- Distinctive: line 128
If current status is "Rejected" and new score < 12: Set status to "Deferred"
- Distinctive: line 134
Update the GitHub Issue body with the new ICE scores and status:
- Very specific: line 136
Use gh issue edit {number} --body "..." to update the issue body with new ICE scores and status
- Very specific: line 137
Add a comment documenting the re-score: "Re-scored: {old_total} → {new_total} (I:{new_i} C:{new_c} E:{new_e}).
- Very specific: line 141
Run .aod/scripts/bash/backlog-regenerate.sh to update the backlog snapshot.
- Distinctive: line 189
Idea not found: Search GitHub Issues by number (NNN, #NNN) or title tag (IDEA-NNN), display error with the identifier that was searched for
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
AOD Re-Score Skill
Purpose
Update an existing idea's ICE (Impact, Confidence, Effort) score when circumstances change, new information emerges, or priorities shift. Reads from and writes to the idea's GitHub Issue.
Source of Truth
GitHub Issues are the sole source of truth for backlog items. All idea state (ICE scores, status, evidence) is stored in the GitHub Issue body. BACKLOG.md is an auto-generated view regenerated from Issues.
Inputs
- NNN, #NNN, or IDEA-NNN (legacy): The identifier of the idea to re-score (from user arguments)
Workflow
Step 1: Parse Input
Extract the idea identifier from user arguments. Accept three formats:
NNN(bare number, e.g.,21): Direct GitHub Issue lookup#NNN(hash-prefixed, e.g.,#21): Strip#prefix, direct lookupIDEA-NNN(legacy, e.g.,IDEA-009): Search issue titles for[IDEA-NNN]bracket tag
If invalid or missing, display usage: Usage: /aod.score NNN (or #NNN or IDEA-NNN)
Step 2: Find GitHub Issue
Search for the matching GitHub Issue:
For numeric input (NNN or #NNN):
source .aod/scripts/bash/github-lifecycle.sh && aod_gh_find_issue NNNFor legacy IDEA-NNN input:
source .aod/scripts/bash/github-lifecycle.sh && aod_gh_find_issue "[IDEA-NNN]"If no issue is found, display an error and exit:
Error: No GitHub Issue found for {identifier}Step 3: Read Current Scores
Read the GitHub Issue body using gh issue view {number} --json body,title. Parse the structured body to extract:
- Description (from
## Ideasection or title) - ICE scores (from
## ICE Scoresection) - Source (from
## Metadatasection) - Status (from
## Metadatasection) - Evidence (from
## Evidencesection)
Step 4: Display Current Scores
Show the existing idea details:
CURRENT SCORES — #{issue_number}
GitHub Issue: #{issue_number}
Idea: {description}
Source: {source}
Date: {date}
Status: {status}
ICE Score: {total} (I:{impact} C:{confidence} E:{effort})
Priority Tier: {tier}Step 5: New ICE Scoring
Present the ICE scoring quick-assessment table using AskUserQuestion. Ask each dimension separately:
Impact — "How much value does this deliver to users?"
Options:
- High (9): "Transformative — significant user value"
- Medium (6): "Solid improvement — meaningful but incremental"
- Low (3): "Minor enhancement — small quality-of-life fix"Allow the user to select "Other" to provide a custom numeric value (1-10).
Confidence — "How sure are we this will succeed?"
Options:
- High (9): "Proven pattern — strong evidence it will work"
- Medium (6): "Some unknowns — reasonable confidence with gaps"
- Low (3): "Speculative — significant uncertainty"Allow the user to select "Other" to provide a custom numeric value (1-10).
Effort (Ease of Implementation) — "How easy is this to build?"
Options:
- High (9): "Days of work — straightforward implementation"
- Medium (6): "Weeks of work — moderate complexity"
- Low (3): "Months of work — significant engineering effort"Allow the user to select "Other" to provide a custom numeric value (1-10).
Step 6: Compute New ICE Total
New ICE Total = Impact + Confidence + Effort
Range: 3-30Step 7: Update Status
Apply status transitions based on threshold crossings:
- If current status is "Deferred" and new score >= 12: Set status to "Scoring"
- If current status is "Scoring" and new score < 12: Set status to "Deferred"
- If current status is "Validated": Preserve status (already PM-approved, do not downgrade)
- If current status is "Rejected" and new score >= 12: Set status to "Scoring" (re-opens for re-validation via
/aod.validate) - If current status is "Rejected" and new score < 12: Set status to "Deferred"
Note: Re-scoring a Rejected idea resets it for a fresh PM review. The PM previously rejected the idea, but re-scoring indicates changed circumstances that warrant re-evaluation. The user must still run /aod.validate to get PM approval.
Step 8: Update GitHub Issue
Update the GitHub Issue body with the new ICE scores and status:
- Use
gh issue edit {number} --body "..."to update the issue body with new ICE scores and status - Add a comment documenting the re-score:
"Re-scored: {old_total} → {new_total} (I:{new_i} C:{new_c} E:{new_e}). Status: {old_status} → {new_status}"
Step 9: Regenerate BACKLOG.md
Run .aod/scripts/bash/backlog-regenerate.sh to update the backlog snapshot.
Step 10: Report Result
Display the comparison:
IDEA RE-SCORED
ID: #{issue_number}
GitHub Issue: #{issue_number}
Idea: {description}
Previous: {old_total} (I:{old_i} C:{old_c} E:{old_e}) — {old_tier}
Updated: {new_total} (I:{new_i} C:{new_c} E:{new_e}) — {new_tier}
{If tier changed: "Priority tier changed: {old_tier} → {new_tier}"}
{If status changed: "Status changed: {old_status} → {new_status}"}
{If status preserved: "Status preserved: {status}"}
Date updated: {YYYY-MM-DD}ICE Scoring Reference
Quick-Assessment Anchors
| Dimension | High (9) | Medium (6) | Low (3) |
| Impact | Transformative | Solid improvement | Minor enhancement |
| Confidence | Proven pattern | Some unknowns | Speculative |
| Effort (Ease) | Days of work | Weeks of work | Months of work |
Priority Tiers
| Score Range | Priority | Action |
| 25-30 | P0 (Critical) | Fast-track to development |
| 18-24 | P1 (High) | Queue for next loop |
| 12-17 | P2 (Medium) | Consider when capacity allows |
| < 12 | Deferred | Auto-defer; requires PM override via /aod.validate |
Auto-Defer Gate
Ideas scoring below 12 are automatically deferred. The PM can override this gate using /aod.validate #NNN.
Edge Cases
- Idea not found: Search GitHub Issues by number (NNN, #NNN) or title tag (IDEA-NNN), display error with the identifier that was searched for
- Invalid ID format: Display usage guidance showing accepted formats (NNN, #NNN, or IDEA-NNN)
- Validated status: Preserve — PM has already approved, re-scoring only updates the numeric score
- Rejected status: Re-opens to Scoring (>= 12) or Deferred (< 12) — allows re-submission to PM via
/aod.validate - Custom ICE score outside 1-10: Clamp to valid range (1 minimum, 10 maximum)
- Score doesn't change: Still update the date to record that a re-evaluation occurred
ghunavailable: Display error — re-scoring requires GitHub access since Issues are the source of truth
Quality Checklist
- Idea identifier parsed and validated (NNN, #NNN, or IDEA-NNN)
- GitHub Issue found for the idea
- Current scores displayed before re-scoring
- New ICE score computed correctly (additive I+C+E)
- Status updated based on threshold crossings (Validated preserved; Rejected re-opens)
- GitHub Issue body updated with new scores
- Re-score documented as Issue comment
- BACKLOG.md regenerated
- Old vs new comparison displayed
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.

