defer-issue

Defers UX options and requirements with six-field traceability and governance for sprint planning and issue triage.

Updated Jan 30, 2019

Search Tags:#workflow #triage #gate #issue-tracking #deferral

Ready to run

npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill defer-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: defer-issue
Source: https://github.com/nishantnaagnihotri/tark-vitark/tree/main/.github/skills/defer-issue
Command: npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill defer-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deferred issue protocol captures decisions, UX options, and requirements gaps that are valid but out of scope for the current slice, ensuring traceability and repeatable re-entry.

Core Features & Use Cases

Enforces a fixed six-field model (Context, Options, Trigger Condition, Prerequisites, Gate Entry Point, References) to describe every deferral.
Provides a clear label taxonomy (deferred, ux, enhancement, question) to categorize and triage deferred work.
Supports triage at Gate 1 by linking deferments to future slices when Trigger Conditions are met.

Quick Start

Create a deferred issue whenever you encounter a decision, UX option, or requirement gap that is out of scope for the current slice, and fill all required fields.

Frequently Asked Questions about defer-issue

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

FAQPage Schema

How do I track out-of-scope decisions during sprint planning without losing context?▼

You can track out-of-scope decisions during sprint planning by creating a deferred issue that enforces a six-field model, capturing Context, Options, Trigger Condition, Prerequisites, Gate Entry Point, and References to ensure reliable traceability and repeatable re-entry.

What is the structured deferral process for issue triage?▼

The structured deferral process for issue triage links valid but out-of-scope requirements to future slices when their Trigger Conditions are met at Gate 1, applying a label taxonomy and triage rules to manage the deferred work.

How do I categorize deferred UX options and requirement gaps for future development slices?▼

You can categorize deferred UX options and requirement gaps using a defined label taxonomy that includes deferred, ux, enhancement, and question labels, ensuring each deferral is properly sorted for future triage.

Do I need to fill all six required fields when deferring an issue?▼

Yes, you need to fill all six required fields when deferring an issue because the fixed model enforces structured traceability and governance, ensuring the deferred decision has clear prerequisites and a defined gate entry point for future triage.

When should I not use a structured deferral protocol for issue tracking?▼

You should not use a structured deferral protocol for issue tracking when work is in scope for the current slice, as this protocol is specifically designed to capture valid but out-of-scope decisions, UX options, and requirement gaps for reliable future re-entry.

Can I use defer-issue to manage requirements gaps in my current sprint?▼

Yes, you can use this deferral approach to manage requirements gaps in your current sprint by capturing them as structured issues with trigger conditions and gate entry points, allowing your team to proceed while ensuring reliable tracking for future slices.