agile-ledger
NewA Claude code skill for Product Management. Plain-Markdown Scrum & Agile product management - ideas → backlog → sprints → releases, plus bug tracking, all from slash commands. Product management in the source code to make it easily accessible to everyone without distractions
Summary
This skill enables product management directly within your codebase using plain Markdown, allowing you to manage ideas, backlogs, sprints, releases, and bug tracking through slash commands.
- It keeps product artifacts close to the source code, making them easily accessible to the entire team without requiring external tools.
Install & Usage
mkdir -p .claude/skillsmkdir -p .claude/skills && curl -o .claude/skills/agile-ledger.md https://raw.githubusercontent.com/nunoamorim99/agile-ledger/main/SKILL.md/agile-ledgerUse Cases
Usage Examples
/agile-ledger add idea 'Implement dark mode toggle'
/agile-ledger create sprint 'Sprint 12' --from-backlog --items 'DARK-1, AUTH-3, PAY-7'
/agile-ledger report release v2.3.0
Security Audits
Frequently Asked Questions
What is agile-ledger?
This skill enables product management directly within your codebase using plain Markdown, allowing you to manage ideas, backlogs, sprints, releases, and bug tracking through slash commands. It keeps product artifacts close to the source code, making them easily accessible to the entire team without requiring external tools.
How to install agile-ledger?
To install agile-ledger: create the skills directory (mkdir -p .claude/skills), then run: mkdir -p .claude/skills && curl -o .claude/skills/agile-ledger.md https://raw.githubusercontent.com/nunoamorim99/agile-ledger/main/SKILL.md. Finally, /agile-ledger in Claude Code.
What is agile-ledger best for?
agile-ledger is a skill categorized under Documentation. Created by nunoamorim99.
What can I use agile-ledger for?
agile-ledger is useful for: Capture a new feature idea from a team discussion and add it to the idea inbox.; Prioritize and move ideas into the product backlog for upcoming sprints.; Plan a sprint by selecting backlog items and assigning them to team members.; Track a bug reported during testing and link it to the relevant release.; Generate a release notes document from completed sprint items.; Review the current sprint status and identify blocked tasks..