select-feature

Score baselined backlog features by value, effort, and dependency status.

11|2|Updated Apr 7, 2022
One-click install
npx skills add https://github.com/nullhack/temple8 --skill select-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: select-feature
Source: https://github.com/nullhack/temple8/tree/main/.opencode/skills/select-feature
Command: npx skills add https://github.com/nullhack/temple8 --skill select-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams automatically identify and select the next highest-value, least-effort feature that is not blocked by dependencies.

Core Features & Use Cases

  • Automated backlog scoring: evaluates value, effort, and dependency status to rank candidates.
  • WSJF-based prioritization: applies a lightweight scoring model to surface the best next item.
  • Guardrails for governance: ensures only baselined, unblocked items are considered and prevents mid-sprint changes.
  • Use Case: When there are multiple backlog items, the skill singles out the top candidate to start next, aligning with the team's feature-lifecycle workflow.

Quick Start

Identify the top eligible backlog feature and move it into in-progress.

Frequently Asked Questions about select-feature

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

FAQPage Schema
How do I prioritize backlog features using WSJF?

Backlog feature prioritization with WSJF scores candidates by value, effort, and dependency status to identify the next item to start. It restricts scoring to baselined features with zero dependencies and enforces zero work-in-progress before selection.

What is the best way to select the next agile feature from a backlog?

The best way to select the next agile feature is to evaluate baselined, unblocked items against a WSJF scoring model. This approach ranks candidates by value and effort, surfacing the highest-value, least-effort feature to move into in-progress.

How does dependency status affect feature selection in product management?

Dependency status restricts feature selection by enforcing that only items with zero dependencies are eligible for scoring. This ensures blocked features are excluded from the backlog evaluation process, preventing mid-sprint delays.

Can I start a new backlog item if my team has work-in-progress?

You cannot start a new backlog item if your team has work-in-progress. The feature selection workflow enforces zero work-in-progress before scoring baselined candidates to ensure focus and prevent context switching.

What happens after the top backlog feature is selected?

After the top backlog feature is selected, it is moved to in-progress and the workflow is documented. The selection process updates WORK.md to reflect the newly started item and maintain accurate feature-lifecycle tracking.