iikit-05-tasks

Generate dependency-ordered task breakdowns from implementation plans and specifications.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill iikit-05-tasks-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iikit-05-tasks
Source: https://github.com/hafidzlvm/opencode/tree/main/.tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-05-tasks
Command: npx skills add https://github.com/hafidzlvm/opencode --skill iikit-05-tasks-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Converting a feature plan and specification into an actionable, ordered list of implementable tasks is error-prone and time-consuming, often missing dependencies, parallelization opportunities, or traceability to requirements. ## Core Features & Use Cases - Dependency-Ordered Task Generation: Produces a tasks.md file organized by phases (Setup, Foundational, User Stories, Polish) with sequential task IDs, parallel [P] markers, and user story labels. - Dependency Graph Validation: Detects circular dependencies, orphan tasks, critical paths, and priority inversions across phases. - Semantic Diff on Re-run: Preserves completed task status and maps old task IDs to new ones when regenerating an existing tasks.md. - Use Case: After running the plan phase for a new API feature, invoke this skill to produce a tasks.md where each contract gets a contract test task, each story is independently implementable, and parallel batches are identified for faster execution. ## Quick Start Ask the AI to generate a dependency-ordered task breakdown from the current feature's plan.md and spec.md into a tasks.md file.

Frequently Asked Questions about iikit-05-tasks

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

FAQPage Schema
How do I break a feature specification into implementable tasks?▼

Run this skill after creating plan.md and spec.md. It extracts the tech stack, user stories, entities, and endpoints, then generates a tasks.md organized by phases with sequential task IDs, parallel markers, and exact file paths.

What task format does the generated tasks.md use?▼

Each task follows the format '- [ ] [TaskID] [P?] [Story?] Description with file path'. The [P] marker indicates parallelizable tasks, and [USn] labels map tasks to user stories for traceability.

Does the task generator work without a testify test specification?▼

Yes, test specifications are optional. If .feature files or test-specs.md exist, tasks reference specific test IDs like TS-001; otherwise tasks are generated from plan and spec content alone.

What happens when I re-run task generation on an existing tasks.md?▼

The skill performs a semantic diff that preserves [x] completion status, maps old task IDs to new ones by similarity, and warns about changes to completed tasks before asking confirmation to overwrite.

Why does the tasks skill report circular dependency errors?▼

The dependency graph validation detects cycles between tasks, orphan tasks with no relationships, backward cross-phase dependencies, and priority inversions where higher-priority stories depend on lower-priority ones.