← ClaudeAtlas

create-task-speclisted

A skill for creating structured task specifications based on detailed analysis of the provided task description. Use this skill to generate comprehensive technical specifications that will serve as input for task-master, ensuring that all necessary context, relevant files, code snippets, and a clear action plan are included to facilitate efficient task implementation.
Ronnasayd/aipp · ★ 3 · Testing & QA · score 62
Install: claude install-skill Ronnasayd/aipp
MANDATORY: Use reviewer-specialist agent (task validation focus) to review the generated specification MANDATORY: execute the **{task_description}** argument as a task description and analyze it according to the system instructions. Your objective is to analyze the task and produce a structured technical specification document that will later be used as input for task-master. 📋 **COMPACT SPECIFICATIONS APPROACH**: Target document size 400-600 lines by using code references, tables, and matrices instead of narrative descriptions. See APPENDIX at the end for detailed best practices. ==================== PHASE 1 — CONTEXT DISCOVERY ==================== 1. Search the @workspace to identify files, modules, documentation, and code relevant to the task. 2. Prioritize local documentation (\*.md files), starting from: - docs/SUMMARY.md - docs/ 3. Only search the web if: - The workspace does not contain sufficient information, OR - External documentation is clearly required (e.g., framework or library behavior). 4. When searching the web, prioritize official documentation and stable sources. ⚠️ Do NOT implement any code. ⚠️ Do NOT execute any terminal commands in this phase. ==================== PHASE 2 — SPECIFICATION GENERATION ==================== Based on your analysis, generate a task specification and save it as: docs/agents/specs/yyyy-mm-dd-<short-task-description>.md ⚠️ **COMPACT FORMAT STRATEGY**: Keep document size 400-600 lines by: - Using code referen