Creates task specification markdown via a five-step interactive protocol.
npx skills add https://github.com/hhk7734/hhk7734 --skill develop-task
Please help me install this Agent Skill. Skill: develop-task Source: https://github.com/hhk7734/hhk7734/tree/main/skills/develop-task Command: npx skills add https://github.com/hhk7734/hhk7734 --skill develop-task
This Skill reduces ambiguity in task creation by ensuring a clear definition of the work and its acceptance criteria.
Describe the task, apply the five-step protocol, and save the result as a markdown file named task.md.
High-intent search queries and answers about installing and using this skill.
To define clear task specifications, use a structured five-step interactive protocol that elicits background, AS-IS, strategic positioning, TO-BE, and actionable items. This process outputs a single markdown file serving as the source of truth for task definitions.
The best way to structure task scoping for handoffs is applying an interactive protocol capturing current state, strategic positioning, and future state. It outputs a markdown file representing the completed task definition to align product and engineering teams.
The five-step task definition protocol works by sequentially extracting background information, AS-IS conditions, strategic positioning, TO-BE goals, and actionable items. It enforces structured task scoping during backlog grooming to ensure alignment on business value.
You do not need any dependencies to create a markdown task definition file. The task scoping protocol operates independently, requiring only a task description to initiate the interactive steps and output the final markdown source of truth.
You need a structured task definition format during feature planning when task ambiguity is high. Applying a five-step protocol to elicit AS-IS and TO-BE states ensures product and engineering teams share a single markdown source of truth.
Task scoping fails without clear acceptance criteria because ambiguity obscures business value and expected outcomes. Defining actionable items and success criteria through a structured protocol prevents misalignment during engineering handoffs and backlog grooming.
pinkroosteraiGenerate actionable feature requests from user input, web research, and codebase analysis.
ucdavisGenerates JIRA tickets with specified metadata from provided titles and notes.
abdullah1854Coordinate Kanban boards with RAG-driven knowledge retrieval and task sync.
daddiaRefine backlog items with five grooming activities for sprint readiness.
