Agent skill

Dex Backlog

by davekilleen in davekilleen/Dex

Show the AI-ranked backlog of Dex system-improvement ideas. An agent skill from davekilleen/Dex.

MITAuto-check passedProduct & Project Management

Install Dex Backlog

skills CLI
$ npx skills add davekilleen/Dex --skill dex-backlog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davekilleen/Dex dex-backlog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dex-backlog .claude/skills/dex-backlog && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dex-backlog
GitHub stars
493
Token cost
~4.5k tokens
SKILL.md length
932 words
Files
1
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Show the AI-ranked backlog of Dex system-improvement ideas. An agent skill from davekilleen/Dex.

  • Works in 6 steps: Load System Context → Score Each Idea → Calculate Weighted Score → …
  • The user says show my Dex ideas
  • SKILL.md covers What This Command Does, Process Overview, Step 1: Load System Context and Step 2: Score Each Idea, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Dex Backlog is an agent skill from davekilleen/Dex. Show the AI-ranked backlog of Dex system-improvement ideas. Use when the user says 'show my Dex ideas', 'what's in the backlog', 'what should we build next'. Not for workshopping one idea into a plan; use dex-improve. Not for discovering existing features; use dex-level-up.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. The repository describes itself as: Your AI Chief of Staff — a personal operating system starter kit that adapts to your role. No coding required. The licence is MIT.

When your agent uses it

  • The user says show my Dex ideas
  • Whats in the backlog
  • What should we build next

Example prompts

  • “show my Dex ideas”
  • “s in the backlog”
  • “what should we build next”
  • “/dex-backlog”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Load System Context
  2. Score Each Idea
  3. Calculate Weighted Score
  4. Update Backlog File
  5. Present Results
  6. Handle Special Cases

What it can do on your machine

Read from SKILL.md and the folder at commit 227f78e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dex Backlog loads about 4.5k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 932 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davekilleen/Dex at commit 227f78e, republished under its MIT licence (© davekilleen). 932 words, ~4,533 tokens.

Download SKILL.mdSave it as .claude/skills/dex-backlog/SKILL.md (or your agent's skills folder).
name
dex-backlog
description
Show the AI-ranked backlog of Dex system-improvement ideas. Use when the user says 'show my Dex ideas', 'what's in the backlog', 'what should we build next'. Not for workshopping one idea into a plan; use `dex-improve`. Not for discovering existing features; use `dex-level-up`.
<!-- Generated from `.claude/skills/dex-backlog/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->

What This Command Does

In plain English: AI-powered ranking of your Dex system improvement backlog based on current system state. Shows you what to build next.

When to use it:

  • Weekly check-in on system improvements
  • After capturing several new ideas
  • When deciding what to work on next
  • During quarterly planning for system improvements

How to run it:

/dex-backlog              # Full review with re-ranking

Process Overview

  1. Load context - Read system state, usage patterns, learnings
  2. Score ideas - Calculate 5-dimension scores for each idea
  3. Re-rank backlog - Sort by weighted total score
  4. Update file - Write new rankings to System/Dex_Backlog.md
  5. Present top ideas - Show top 5 with "Why now?" justification
  6. Offer next steps - Workshop, implement, or defer

Step 1: Load System Context

Read these files to understand current system state:

Required Files
System/Dex_Backlog.md              # All ideas to score
System/usage_log.md                # Feature adoption patterns
System/user-profile.yaml           # Role, preferences
CLAUDE.md                          # Current capabilities
Optional Files (if they exist)
System/Session_Learnings/           # Recent pain points (last 30 days)
.claude/commands/                  # Available commands
core/mcp/                          # MCP integrations
06-Resources/Learnings/               # Captured patterns
Extract Context

Build a context dictionary with:

  • Usage patterns: Which features are used vs. unused
  • Role profile: PM, Sales, Leadership, Engineer, etc.
  • Pain points: Recent friction from session learnings
  • System capabilities: What's currently available
  • Backlog state: All ideas and their current scores

Step 2: Score Each Idea

For every active idea in the backlog, calculate 5 dimension scores.

⚠️ CURSOR FEASIBILITY CHECK (Do This First!)

Before scoring ANY idea, validate it's actually implementable in Cursor:

What Cursor/Terminal CAN do:

  • ✅ Read and write files
  • ✅ Execute shell commands
  • ✅ Build MCP tools for structured operations
  • ✅ Parse and transform file contents
  • ✅ Create caches and indexes (file-based)
  • ✅ Run commands on schedules or triggers

What Cursor/Terminal CANNOT do:

  • ❌ Track user edits in real-time
  • ❌ Hook into Cursor internals
  • ❌ Monitor user actions passively
  • ❌ Access edit history without explicit file reads
  • ❌ Real-time background processes watching for changes

If idea requires something from the CANNOT list → Set all scores to 0 and flag as "Not feasible in Cursor"


After feasibility check passes, score on 5 dimensions:

Dimension 1: Impact (35% weight)

Question: How much would this improve daily workflow?

Scoring logic:

Base score: 50

+20 if matches_recent_pain_points():
  - Search System/Session_Learnings/ for mentions of this issue
  - Keywords from idea title/description appear in learnings
  - Problem stated explicitly in recent notes

+15 if affects_daily_workflow():
  - Touches commands used >3x per week (from usage_log)
  - Modifies core files (03-Tasks/Tasks.md, daily plans, person pages)
  - Impacts repetitive actions

+15 if has_compound_value():
  - Enables other ideas in backlog
  - Reduces technical debt
  - Creates reusable patterns
  - Unblocks multiple workflows

Max: 100

Examples:

  • "Auto-suggest person pages": 95 (daily workflow + enables relationship tracking)
  • "Export to blog": 40 (nice-to-have, doesn't affect core workflow)

Dimension 2: Alignment (20% weight)

Question: Does this fit actual usage patterns?

Scoring logic:

Base score: 50

+30 based on usage_overlap():
  - Extract features idea depends on
  - Check if those features are used (usage_log)
  - Calculate overlap: (used_features / total_features) * 30

+20 if fits_role_profile():
  - PM roles: prioritize project/product features
  - Sales roles: prioritize relationship/account features
  - Leadership: prioritize synthesis/review features
  - Match category to role focus areas

Max: 100

Examples:

  • Idea needs "person pages" → Check if user has created person pages
  • If usage_log shows person pages = used → Higher alignment
  • If role = PM and idea = product features → +20 role fit

Dimension 3: Token Efficiency (20% weight)

Question: Does this reduce context/token usage?

CRITICAL - Cursor Feasibility Check: Before scoring, verify the idea is implementable in Cursor/Terminal:

  • ✅ Can use: File read/write, MCP tools, command execution, file-based caching
  • ❌ Cannot use: Real-time edit tracking, Cursor internal hooks, monitoring user actions
  • If not feasible in Cursor → Score = 0 on all dimensions

Scoring logic:

Base score: 50

+25 if reduces_token_usage():
  - Caches/stores frequently accessed data (in files/MCP)
  - Compresses or summarizes verbose content (file-based)
  - Eliminates redundant reads
  - Enables more efficient retrieval patterns

+15 if improves_context_efficiency():
  - Reduces number of files that need reading
  - Creates structured summaries (YAML/JSON files)
  - Better indexing/search to avoid broad scans
  - Moves data from markdown to structured format

+10 if enables_incremental_updates():
  - Supports partial updates instead of full rewrites
  - Tracks changes in separate files
  - Lazy loading or on-demand computation

Max: 100

Examples:

  • "Cache meeting summaries in YAML": 90 (file-based, avoids re-reading)
  • "Track user edits for learning": 0 (NOT FEASIBLE - can't track edits)
  • "Add new field to template": 50 (neutral token impact)

Dimension 4: Memory & Learning (15% weight)

Question: Does this enhance system memory, persistence, or self-learning?

Scoring logic:

Base score: 50

+20 if improves_memory_persistence():
  - Stores learnings for future reference
  - Creates retrievable knowledge base
  - Captures patterns that compound over time
  - Builds historical context

+20 if enables_self_learning():
  - System learns from user behavior
  - Adapts recommendations based on patterns
  - Builds preference models
  - Improves predictions over time

+10 if creates_feedback_loops():
  - Tracks outcomes of suggestions
  - Measures effectiveness of recommendations
  - Refines based on what works

Max: 100

Examples:

  • "Learning pattern synthesizer": 95 (captures + compounds knowledge)
  • "Preference learning from edits": 85 (system adapts over time)
  • "Static template update": 50 (no learning component)

Dimension 5: Proactivity (10% weight)

Question: Does this enable proactive concierge behavior?

Scoring logic:

Base score: 50

+25 if enables_anticipation():
  - Surfaces relevant info before asked
  - Predicts needs based on patterns
  - Proactive suggestions not just reactive
  - Context-aware prompts

+15 if automates_routine_decisions():
  - Handles repetitive choices automatically
  - Learns user preferences and applies them
  - Reduces decision fatigue

+10 if improves_timing():
  - Right information at right time
  - Context-aware interruptions
  - Anticipates upcoming needs

Max: 100

Examples:

  • "Auto-prep meetings based on calendar": 90 (proactive + anticipatory)
  • "Suggest weekly priorities from patterns": 80 (learns and anticipates)
  • "Add manual review step": 50 (reactive, not proactive)

Step 3: Calculate Weighted Score

total_score = (
  (impact * 0.35) +
  (alignment * 0.20) +
  (token_efficiency * 0.20) +
  (memory_learning * 0.15) +
  (proactivity * 0.10)
)

Round to integer: total_score = round(total_score)

Priority Bands:

  • High Priority (85+): Should tackle soon, high ROI
  • Medium Priority (60-84): Good ideas, right time matters
  • Low Priority (<60): Maybe later or needs refinement

Why These Dimensions:

  • Effort excluded: With AI coding, implementation is cheap - focus on value, not cost
  • Token efficiency prioritized: Context efficiency is critical for performance
  • Memory & learning emphasized: System should get smarter over time
  • Proactivity valued: Concierge behavior > reactive tool

Show full SKILL.md (363 more words)Show less

Step 4: Update Backlog File

Rewrite System/Dex_Backlog.md with:

  1. Update timestamp at top
  2. Re-sort ideas by total score (high to low)
  3. Update each idea with new scores:
    markdown
    - **[idea-XXX]** Title
      - **Score:** 92 (Impact: 95, Alignment: 90, Effort: 85, Synergy: 95, Fresh: 70)
      - **Category:** category
      - **Captured:** YYYY-MM-DD
      - **Why ranked here:** [1-2 sentence reasoning based on scores]
      - **Description:** [original description]
  4. Place in correct section (High/Medium/Low priority)
  5. Preserve Archive section (don't re-rank implemented ideas)

Step 5: Present Results

Show the user the top 5 ideas with context:

markdown
# 📊 Backlog Review Complete

*Analyzed {{total_ideas}} ideas against current system state*

## 🔥 Top 5 Recommendations

### 1. [idea-XXX] {{title}} (Score: {{score}})

**Why now:** {{reasoning based on scores - be specific}}

**Quick assessment:**
- Impact: {{impact_justification}}
- Fits your patterns: {{alignment_justification}}
- Effort: {{effort_estimate}}

**Next step:** Run `/dex-improve "{{title}}"` to workshop this idea

---

### 2. [idea-YYY] {{title}} (Score: {{score}})

[Same format]

---

[... continue for top 5 ...]

---

## 📈 Backlog Health

- **Total ideas:** {{total}}
- **High priority (85+):** {{high_count}}
- **Medium priority (60-84):** {{medium_count}}
- **Low priority (<60):** {{low_count}}

{{#if high_count > 5}}
⚠️ **Note:** You have {{high_count}} high-priority ideas. Consider tackling 1-2 this week to reduce backlog.
{{/if}}

{{#if low_count > 10}}
💡 **Tip:** {{low_count}} low-priority ideas might be worth archiving or refining.
{{/if}}

---

## What would you like to do?

1. **Workshop an idea** → `/dex-improve "[title]"`
2. **Capture a new idea** → Use `capture_idea` MCP tool
3. **Mark one implemented** → Use `mark_implemented` MCP tool
4. **View full backlog** → Check `System/Dex_Backlog.md`

Step 6: Handle Special Cases

If Backlog is Empty
markdown
# 📊 Backlog Review

Your backlog is empty! 

Start capturing improvement ideas:
- Use the `capture_idea` MCP tool anytime you think "I wish Dex did X"
- Run `/dex-improve` to explore capability gaps
- Run `/dex-level-up` to discover unused features

The backlog system will help you track and prioritize ideas systematically.
If No High Priority Ideas
markdown
🎉 **Good news:** No urgent improvements needed!

Your system is working well. The backlog has ideas for later, but nothing critical right now.

Consider:
- Running `/dex-level-up` to discover unused features
- Capturing ideas as they come up
- Reviewing backlog quarterly
If Many Stale Ideas (>6 months old)
markdown
⚠️ **Backlog maintenance needed**

You have {{stale_count}} ideas older than 6 months. These might be:
- No longer relevant → Archive them
- Still valuable but not urgent → Keep them
- Worth revisiting with new context → Re-evaluate descriptions

Review stale ideas:
{{list stale ideas}}

Want to bulk archive these? I can help clean up the backlog.

Integration with Other Commands

Hand-off to /dex-improve

When user says "Let's work on #1" or "Workshop idea-XXX":

  1. Read the idea details from backlog
  2. Pass to /dex-improve with context:
    /dex-improve "{{idea_title}}"
    
    Context from backlog:
    - Current score: {{score}}
    - Why it's prioritized: {{reasoning}}
    - Original description: {{description}}
  3. /dex-improve takes over for workshopping

Scoring Implementation Tips

Cursor Feasibility Check (Run FIRST)
python
def check_cursor_feasibility(idea: dict) -> dict:
    """
    Returns: {
        'feasible': bool,
        'reason': str,
        'capabilities_required': list
    }
    """
    description_lower = idea['description'].lower()
    
    # Red flags - things Cursor CAN'T do
    cannot_do = {
        'track edits': 'Cannot monitor file edits in real-time',
        'watch user': 'Cannot observe user actions passively',
        'hook into': 'Cannot hook into Cursor internals',
        'monitor changes': 'Cannot monitor without explicit file reads',
        'background process': 'No persistent background processes'
    }
    
    for phrase, reason in cannot_do.items():
        if phrase in description_lower:
            return {
                'feasible': False,
                'reason': reason,
                'suggestion': 'Reframe as file-based or command-triggered'
            }
    
    # Green flags - things Cursor CAN do
    can_do = ['file', 'read', 'write', 'mcp', 'command', 'cache', 'index', 'parse']
    has_feasible_approach = any(word in description_lower for word in can_do)
    
    if has_feasible_approach:
        return {'feasible': True, 'reason': 'Uses Cursor-compatible operations'}
    else:
        return {
            'feasible': False,
            'reason': 'No clear implementation path in Cursor',
            'suggestion': 'Add file-based or MCP approach'
        }
For Impact Calculation
python
def calculate_impact(idea, context):
    # First check feasibility
    feasibility = check_cursor_feasibility(idea)
    if not feasibility['feasible']:
        return 0  # Not feasible = 0 impact
    
    score = 50
    
    # Check session learnings for pain point mentions
    learnings = context['session_learnings']
    idea_keywords = extract_keywords(idea['title'] + idea['description'])
    
    for learning in learnings:
        learning_keywords = extract_keywords(learning['content'])
        if overlap(idea_keywords, learning_keywords) > 0.3:
            score += 20
            break
    
    # Check if affects daily workflow
    if touches_daily_commands(idea, context['usage_log']):
        score += 15
    
    # Check compound value
    if enables_other_ideas(idea, context['backlog']):
        score += 15
    
    return min(score, 100)
For Alignment Calculation
python
def calculate_alignment(idea, context):
    score = 50
    
    # Extract related features
    features = extract_related_features(idea)
    used_features = get_used_features(context['usage_log'])
    
    overlap_ratio = len(features & used_features) / len(features)
    score += int(overlap_ratio * 30)
    
    # Role fit
    role = context['user_profile']['role']
    category = idea['category']
    
    role_fit_map = {
        'PM': ['projects', 'workflows', 'knowledge'],
        'Sales': ['relationships', 'tasks'],
        'Leadership': ['knowledge', 'workflows']
    }
    
    if category in role_fit_map.get(role, []):
        score += 20
    
    return min(score, 100)
For Token Efficiency Calculation
python
def calculate_token_efficiency(idea, context):
    score = 50
    
    # Check if reduces token usage
    if reduces_reads(idea):  # Caching, summaries
        score += 25
    
    # Context efficiency improvements
    if improves_retrieval(idea):  # Better indexing, structured data
        score += 15
    
    # Incremental updates
    if supports_incremental(idea):  # Partial updates, lazy loading
        score += 10
    
    return min(score, 100)
For Memory & Learning Calculation
python
def calculate_memory_learning(idea, context):
    score = 50
    
    # Memory persistence
    if stores_learnings(idea):  # Knowledge base, historical context
        score += 20
    
    # Self-learning capability
    if enables_adaptation(idea):  # Learns from behavior, improves over time
        score += 20
    
    # Feedback loops
    if tracks_outcomes(idea):  # Measures effectiveness, refines
        score += 10
    
    return min(score, 100)
For Proactivity Calculation
python
def calculate_proactivity(idea, context):
    score = 50
    
    # Anticipation capability
    if enables_anticipation(idea):  # Surfaces info before asked
        score += 25
    
    # Automation of routine decisions
    if automates_decisions(idea):  # Handles repetitive choices
        score += 15
    
    # Timing improvements
    if improves_timing(idea):  # Right info at right time
        score += 10
    
    return min(score, 100)

Best Practices

  1. Run weekly during /week-plan or standalone
  2. Don't obsess over scores - they're guidance, not gospel
  3. Trust your instinct - high score + gut feel = go
  4. Keep backlog lean - max 20 active ideas
  5. Archive implemented - celebrate progress
  6. Refine low scorers - add detail to boost alignment/impact

Philosophy

The backlog isn't a todo list - it's a decision support system.

Scores help you:

  • Surface high-value work
  • Avoid shiny object syndrome
  • Align improvements with actual usage
  • Make intentional choices

But you're still the decision maker. If a low-scoring idea excites you, workshop it. The system serves you, not the other way around.


Track Usage (Silent)

Call the mark_feature_used tool on the dex-analytics MCP server with dex-backlog. This ticks the feature's box in System/usage_log.md, which is what /dex-level-up reads to recommend features that have not been tried. It writes locally and sends nothing, so it runs whether or not analytics is enabled.

Analytics (Silent):

Call track_event with event_name backlog_reviewed and properties:

  • ideas_count

This only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".

© davekilleen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/dex-backlog of davekilleen/Dex.

Open the folder on GitHubat commit 227f78e

Compare with similar skills

Dex Backlog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dex Backlog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dex Backlog this skilldavekilleen/Dex493—~4.5kAutomated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed
  • A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes
  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from davekilleen/Dex

All 61 skills in this repo
  • Dspy Ruby

    davekilleen/Dex

    This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications.

    493 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Diff Adopt Profile

    davekilleen/Dex

    Adopt a full published Heydex profile by handle ('set me up like @davekilleen').

    493 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Diff Generate

    davekilleen/Dex

    Package one workflow — how you use Dex for a specific job — into a shareable DexDiff methodology doc.

    493 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Creating Agent Skills

    davekilleen/Dex

    Expert guidance for creating, writing, and refining Claude Code Skills.

    493 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Feedback

    davekilleen/Dex

    Report a Dex bug to the Dex team with zero homework — Dex investigates locally, builds a privacy-safe report, shows it to you (or auto-sends if you've chosen that), and tracks the ticket until it's…

    493 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Dhh Rails Style

    davekilleen/Dex

    This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style.

    493 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Questions about Dex Backlog

What does Dex Backlog do?

Show the AI-ranked backlog of Dex system-improvement ideas. An agent skill from davekilleen/Dex. Dex Backlog is an agent skill from davekilleen/Dex. Show the AI-ranked backlog of Dex system-improvement ideas.

When should I use Dex Backlog?

Dex Backlog fits situations like: the user says show my Dex ideas; whats in the backlog; what should we build next.

How do I install Dex Backlog in Claude Code?

Run `npx skills add davekilleen/Dex --skill dex-backlog -a claude-code`. Or copy the skill folder (.agents/skills/dex-backlog in davekilleen/Dex) into .claude/skills/dex-backlog in your project. Claude Code loads it when a task matches its description.

How do I install Dex Backlog in Codex?

Run `npx skills add davekilleen/Dex --skill dex-backlog -a codex`. Or copy the skill folder (.agents/skills/dex-backlog in davekilleen/Dex) into .agents/skills/dex-backlog in your project. Codex loads it when a task matches its description.

Can I use Dex Backlog in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davekilleen/Dex --skill dex-backlog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dex-backlog, .gemini/skills/dex-backlog, .github/skills/dex-backlog and .opencode/skills/dex-backlog in your project.

What does Dex Backlog need to run?

SKILL.md names no scripts, command-line tools or credentials: Dex Backlog is instructions for the agent only.

Does Dex Backlog access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dex Backlog safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dex Backlog use?

Dex Backlog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dex Backlog use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dex Backlog?

Skills that share tags, products or a category with Dex Backlog: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dex Backlog?

davekilleen (a GitHub user) maintains it in davekilleen/Dex, which has 493 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 8, 2026.

Source: davekilleen/Dex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.