tasks-init

Generate a structured TASKS.md scaffold with domain-guarded tasks from codebase analysis.

17|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/insightflo/claude-impl-tools --skill tasks-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tasks-init
Source: https://github.com/insightflo/claude-impl-tools/tree/main/plugin/skills/tasks-init
Command: npx skills add https://github.com/insightflo/claude-impl-tools --skill tasks-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

TASKS.md scaffolding helps teams quickly generate a structured TASKS.md at project start or when tasks are missing by analyzing the codebase and applying Specialist context injection.

Core Features & Use Cases

  • Interactive collection of project information (project name, features, analysis results) to tailor tasks.
  • Automatic generation of dependency-aware tasks across T0 to T3 with domain-guarded structure (backend, frontend, shared).
  • Integration with code analysis to surface tech stacks, directory structure, and existing TODO markers for informed planning.
  • Output a ready-to-edit TASKS.md that can be executed with Claude workflows or hands-on execution.

Quick Start

Run the task-init workflow to generate TASKS.md in the project root and review the suggested tasks.

Frequently Asked Questions about tasks-init

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

FAQPage Schema
How do I generate a structured TASKS.md scaffold for my repository?▼

Generate a TASKS.md scaffold by running the task-init workflow, which analyzes your codebase to detect project features, tech stack, and domains, then produces a multi-phase task file with dependency-aware tasks for backend, frontend, and shared areas.

What is domain-driven task generation and how does it structure project planning?▼

Domain-driven task generation structures project planning by analyzing your codebase to identify backend, frontend, and shared domains, then creating domain-guarded tasks across phases T0 to T3 with included dependencies, risks, owners, and metadata to support orchestration.

How do I extract existing TODO markers and tech stack details for project planning?▼

Extract existing TODO markers and tech stack details by running the task-init workflow, which performs code analysis to surface directory structures, technologies, and incomplete markers, using them to inform the generated multi-phase TASKS.md planning document.

Can I automatically create dependency-aware tasks across multiple project phases?▼

Yes, you can automatically create dependency-aware tasks across T0 to T3 phases by running the task-init workflow, which interactively collects project information and generates a structured TASKS.md with domain-guarded tasks including dependencies, risks, and file references.

Does the TASKS.md scaffolding workflow work without external dependencies?▼

Yes, the TASKS.md scaffolding workflow works without external dependencies, using internal scripts to analyze your repository and interactively generate a ready-to-edit task structure tailored to your specific codebase and tech stack.

What is the best way to initialize a multi-phase task list for a new software project?▼

The best way to initialize a multi-phase task list is to use interactive scaffolding that analyzes your codebase to produce a T0–T3 structured TASKS.md, complete with domain-guarded tasks, owners, and metadata for immediate team collaboration.