skills.rest
e2its
e2itsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

factory-backlog-next-task

Parse execution plans and linked issues to compute the next backlog task.

1|Updated Apr 8, 2026
Search Tags:#backlog#sdlc#execution-plan#project-tracking#dependency-validation#task-sequencing#issue-enrichment
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-backlog-next-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: factory-backlog-next-task
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-backlog-next-task
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-backlog-next-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates guesswork when determining the next executable task in a project's backlog sequence, removing the need to manually cross-reference execution plans, dependency status, and linked issue tracking data to know exactly what to run next.

Core Features & Use Cases

  • Fast Cache Lookup: Returns the next task instantly if the execution plan hasn't changed since last sync, skipping redundant parsing.
  • Authoritative Plan Parsing: Reads the project's official execution plan to find the first pending unchecked task and validates dependencies to flag blockers.
  • Issue Context Enrichment: Fetches full details from linked project tracking issues (GitHub, Jira, Linear, etc.) to pull acceptance criteria, definition of done, and the authoritative "Comando Factory" command, surfacing any mismatches with the execution plan.
  • Use Case: A development team using a governed SDLC can use this Skill after completing a feature to immediately get the exact agent, command, and context for the next task, without manual coordination.

Quick Start

Ask the factory-backlog-next-task skill to identify the next executable backlog step for your current project, including the required agent, command, and any linked issue context.

Frequently Asked Questions about factory-backlog-next-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine the next executable task in a backlog sequence without manual tracking?▼

To determine the next executable task in a backlog sequence, parse the authoritative project execution plan to find the first pending unchecked item. Cross-referencing linked issue tracking data validates dependencies and flags potential blockers automatically.

How does dependency validation work when sequencing backlog tasks from an execution plan?▼

Dependency validation works by cross-referencing the authoritative execution plan with linked issue tracking data. This process identifies the first pending unchecked task, verifies its dependencies are met, and flags any blockers that prevent task sequencing.

Can I use linked GitHub Issues or Jira data to enrich context for the next backlog task?▼

Yes, you can enrich context for the next backlog task using linked GitHub Issues, Jira, or Linear data. The system fetches full issue details, pulling acceptance criteria, definition of done, and the exact command to execute.

What is the best way to detect discrepancies between an execution plan summary and issue tracking commands?▼

The best way to detect discrepancies between an execution plan summary and issue tracking commands is to cross-reference the parsed plan against authoritative linked issues. This surfaces any mismatches between planned summaries and the actual issue commands.

Does backlog task sequencing support fast cache lookup if the execution plan hasn't changed?▼

Yes, backlog task sequencing supports fast cache lookup. If the execution plan hasn't changed since the last sync, the system returns the next task instantly by skipping redundant parsing of the authoritative plan.

Why does my next backlog task show a blocker even though it is the first pending item in the execution plan?▼

Your next backlog task shows a blocker because dependency validation failed during cross-referencing. Even as the first pending unchecked item, unresolved dependencies in linked issue tracking data will flag it as blocked.

Related Skills

Explore More Software Engineering Skills→
elijahmurrayelijahmurray
2

setup-ticket-system

Configure GitHub Issues, Linear, Jira, or GitLab for issue tracking.

Community
Basic
takusaotometakusaotome
5

completion-quality-gate-designer

Design evidence-based quality gates with entry and exit criteria for release readiness.

Community
Advanced
erankavijaerankavija

jit-manage

Manage JIT issue lifecycle with automated gates and dependency tracking.

Community
Advanced
walter-lawalter-la

dummy-01-intake

Parse unstructured issue descriptions to classify task types and output structured data.

Community
Basic