Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
gentleman-programming avatar

Engram Backlog Triage

  • 48 installs
  • 5.8k repo stars
  • Updated July 30, 2026
  • gentleman-programming/engram

Part of the Engram spec-driven development system, oriented toward triaging and prioritizing backlog items within the multi-phase implementation workflow.

About

An Engram skill within a spec-driven development toolkit that supports coordinating and planning work across spec, design, implementation, and validation. A developer uses it when triaging a backlog inside the Engram workflow.

  • Part of the Engram spec-driven development skill set
  • Supports multi-phase implementation planning

Engram Backlog Triage by the numbers

  • 48 all-time installs (skills.sh)
  • Ranked #1,641 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gentleman-programming/engram --skill engram-backlog-triage

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs48
repo stars5.8k
Last updatedJuly 30, 2026
Repositorygentleman-programming/engram

What it does

Part of the Engram spec-driven development system, oriented toward triaging and prioritizing backlog items within the multi-phase implementation workflow.

Files

SKILL.mdMarkdownGitHub ↗

When to Use

Use this skill when:

  • Starting non-trivial changes
  • Coordinating spec, design, implementation, and validation
  • Running command-based SDD flow

---

Canonical Phase Order

1. explore - understand existing behavior and constraints 2. propose - define intent and scope 3. apply - implement tasks from approved plan 4. verify - validate behavior against spec and regressions 5. archive - capture completion and close loop

Never skip a phase without explicit rationale.

---

Artifacts per Phase

  • Explore: findings and risks
  • Propose: change proposal with scope boundaries
  • Apply: code + tests
  • Verify: evidence of validation
  • Archive: finalized summary and follow-ups

---

Exit Criteria

  • [ ] Scope and risks understood before implementation
  • [ ] Tests prove expected behavior
  • [ ] Verification covers regressions
  • [ ] Session summary captures learnings for next work

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.