create-task-spec

Create task specifications with embedded context and architecture references.

2|2|Updated Oct 28, 2025

Search Tags:#workflow #embedded context #task spec #architecture references

Ready to run

npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill create-task-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-task-spec
Source: https://github.com/adolfoaranaes12/BMAD-ENHANCED/tree/main/.claude/skills/create-task-spec
Command: npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill create-task-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires template-task, and includes templates (resource) and references (resource) components.

What problem does it solve?

This Skill creates hyper-detailed task specifications with embedded context and architecture references to eliminate lookup during implementation.

Core Features & Use Cases

Generate task spec with objective, ACs, context, and dependencies
Link to architecture and standards references
Produce ready-to-use task files for execution

Quick Start

Create a task spec for a feature and embed essential context and references.

Frequently Asked Questions about create-task-spec

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

FAQPage Schema

How do I create a detailed task specification with embedded architecture context?▼

Task specs embed objective, acceptance criteria, dependencies, and architecture references in a single document. This Skill generates high-density specs that eliminate implementation lookups by bundling context, source citations, testing guidelines, and standards references into ready-to-execute task files for backend, API, and frontend work.

What should I include in a task spec to hand off to developers?▼

Comprehensive task specs require objective, acceptance criteria, embedded context, architecture references, validation checkpoints, and testing guidelines. This Skill produces task files with all these elements interconnected, reducing back-and-forth questions during implementation and ensuring developers have full context without external lookups.

Can I break down a feature into sequential tasks with this approach?▼

Yes, this Skill breaks features into 3–15 sequential tasks, each with validation checkpoints and embedded context. Tasks for backend, API, and frontend work are generated with linked architecture references and testing requirements, enabling parallel or staged execution with built-in verification steps.

How do task specs reduce implementation time?▼

Task specs with embedded context eliminate handoff delays by including architecture references, source citations, and testing guidelines upfront. Developers execute without searching documentation, referencing external standards, or requesting clarification, compressing timeline from discovery to delivery.

What's the difference between a task spec and a feature description?▼

Feature descriptions state what to build; task specs detail how to build it. Task specs add acceptance criteria, validation checkpoints, architecture references, context-rich documentation, and sequential task breakdown, transforming a requirement into an execution roadmap ready for immediate developer handoff.

Do task specs work for backend, API, and frontend work simultaneously?▼

Yes, this Skill generates task specs for backend, API, and frontend work with aligned validation checkpoints and shared architecture context. Sequential task structure and embedded dependencies enable coordinated execution across layers while maintaining consistency through referenced standards and architecture guidelines.