Feature Decision: [Feature Name]

Purpose

Make and document feature prioritization decisions with a structured framework. Ensures key factors are considered, stakeholders are consulted, and rationale is preserved for future reference.

Evidence, authority, and recovery

Treat this skill as decision support: a recommendation is analysis, while the decision belongs to an identified human authority.

• Attach a source ID or path, source date, and as-of date to every material claim, quote, estimate, stakeholder input, and roadmap fact. Keep the evidence date separate from the date the human confirms a decision.
• Expose unknown effort and unknown evidence as first-class values. Unknown effort is not Small, and missing evidence is not evidence of no impact; name the missing input or assumption instead of choosing a convenient rating. Preserve contradictory evidence with both sources and dates rather than reconciling it silently.
• Never invent absent customer names, user counts, revenue, effort estimates, dates, stakeholder alignment, owners, quotes, or dependencies. If a field is not supported, record unknown or not provided and explain what would resolve it.
• Keep the recommendation separate from the decision authority: label the output Recommendation and Human decision authority separately. Recommendations are not human decisions; only the human authority may choose or confirm Go, No-Go, or Defer.
• Before creating or updating a decision document, search for existing decisions for the feature and show an exact preview: target path, create/update operation, and complete proposed contents or diff. Require explicit confirmation from the human authority before any change.
• Preserve each earlier decision. Never overwrite it silently: append a dated decision entry when extending the record, or explicitly supersede the earlier decision with the human authority, reason, and link recorded.
• After an approved write, read back the target and compare it with the confirmed preview. If the write fails or the read-back differs, report the exact failure, leave the earlier decision intact, do not claim the document was created or updated, and recover by re-reading the current file and presenting a new preview for explicit confirmation.

Usage

• /feature-decision [feature-name] - Make a decision on a specific feature
• /feature-decision - Start decision process with guided questions

Method

Define the decision question, options, constraints, planning horizon, and named human decision authority. Gather dated customer, strategic, delivery, design, commercial, and dependency evidence into a source ledger. Use only a configured or user-confirmed sizing scale; if no scale or estimate exists, preserve effort as Unknown. Compare options and trade-offs, expose assumptions and conflicting evidence, and produce a recommendation without converting it into a decision. Search prior decision records before proposing any save, preserving their history and requiring separate confirmation for a new or superseding entry.

Output contract

Return the decision question, authority, scope and evidence coverage, options, source-backed impact and effort assessment, unknowns, contradictions, trade-offs,