create-task

Generate structured Minsky task specifications with Summary, Success Criteria, Scope, Acceptance Tests, and Context.

6|1|Updated Apr 26, 2025
One-click install
npx skills add https://github.com/edobry/minsky --skill create-task-edobry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-task
Source: https://github.com/edobry/minsky/tree/main/.claude/skills/create-task
Command: npx skills add https://github.com/edobry/minsky --skill create-task-edobry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured, high-quality task specification for Minsky tasks, ensuring clear criteria and context.

Core Features & Use Cases

  • Generate a comprehensive spec including Summary, Success Criteria, Scope, Acceptance Tests, and Context.
  • Analyze user intent and, if needed, research the codebase to ground the spec in reality.
  • Produce a ready-to-create task spec that reduces back-and-forth and accelerates planning.

Quick Start

Describe a task you want to create and let the skill generate a complete, structured spec.

Frequently Asked Questions about create-task

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

FAQPage Schema
How do I generate a structured task specification for a new software feature?

To generate a structured task specification, describe the feature intent and the tool analyzes the codebase to produce a spec with Summary, Success Criteria, Scope, Acceptance Tests, and Context sections.

What should be included in software task acceptance tests and scope definitions?

Task acceptance tests and scope definitions should include clear success criteria, explicit boundaries of what the task covers, and contextual references to related code paths or issues to guide implementation effectively.

How do I create a task spec that is grounded in my actual codebase?

To create a codebase-grounded task spec, provide your user intent and the tool researches your existing code paths and issues, embedding those references directly into the generated specification's Context section.

Can I use this approach to reduce planning back-and-forth for new development tasks?

Yes, generating a ready-to-create task spec reduces planning back-and-forth by producing a comprehensive, structured document upfront that satisfies requirements and aligns stakeholders before implementation begins.

What is the best way to document requirements for a new coding task?

The best way to document requirements is using a structured template that captures user intent, success criteria, scope, and acceptance tests, ensuring the resulting task spec is ready for immediate creation.