deep-task

Generate Task.md specifications for one-time code change workflows.

3|3|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hs3180/disclaude --skill deep-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-task
Source: https://github.com/hs3180/disclaude/tree/main/skills/deep-task
Command: npx skills add https://github.com/hs3180/disclaude --skill deep-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes user requests to create Task.md specification files that trigger a full dialogue workflow (Evaluator → Executor → Reporter) for one-time code changes, bug fixes, or feature implementations.

Core Features & Use Cases

  • Analyze user requests and extract clear Task.md specifications
  • Write Task.md to the correct path tasks/{MessageID}/task.md with description, requirements, and verification steps
  • Enable automatic dialogue phases (Evaluator → Executor → Reporter) once Task.md is detected
  • Enforce one-time-task scope (not for scheduled tasks) and provide guardrails for ambiguous requests

Quick Start

Clarify any ambiguities in the user's request and then generate a Task.md at the appropriate path describing the task.

Frequently Asked Questions about deep-task

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

FAQPage Schema
How do I generate task specifications for automated code review workflows?

You generate task specifications by providing a user request for a one-time code change, which the Skill analyzes to create a Task.md file containing descriptions, requirements, and verification steps.

What is a dialogue workflow for one-time code refactoring tasks?

A dialogue workflow for one-time code refactoring is an automated sequence of Evaluator, Executor, and Reporter phases triggered by a Task.md file to evaluate, execute, and report code changes.

Can I use this task generation workflow for scheduled or recurring software engineering tasks?

No, this task generation workflow enforces a one-time-task scope and is specifically designed for bug fixes, feature implementations, and refactoring tasks rather than scheduled or recurring automation.

How do I handle ambiguous requests when initializing task generation?

When initializing task generation, the workflow provides guardrails for ambiguous requests by clarifying any ambiguities in the user's input before generating the Task.md specification at the appropriate path.

Does this task generation workflow require any external dependencies or components?

No, this task generation workflow operates without any external dependencies or components, relying solely on user request analysis to produce the Task.md specification and trigger the dialogue workflow.