bundle-tasks

Bundles 2-6 related tasks into one meta-task with verbatim preservation and auto-archive.

6|Updated May 18, 2026
One-click install
npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill bundle-tasks-mokhtarabadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bundle-tasks
Source: https://github.com/mokhtarabadi/cognitive-lead-hq/tree/main/skill-templates/bundle-tasks
Command: npx skills add https://github.com/mokhtarabadi/cognitive-lead-hq --skill bundle-tasks-mokhtarabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing many small related tasks one-by-one through a full backlog → in-progress → qa → completed Kanban cycle creates repetitive overhead. This Skill merges 2-6 small related tasks into a single META task with one branch, one git diff, and one all-or-nothing QA gate. ## Core Features & Use Cases - Verbatim Preservation: Copies every source task's Goal, Acceptance Criteria, Local TODOs, and Risk & Rollback sections verbatim into the META file, with a checksum validation that fails if any text is dropped. - Transactional Auto-Archive: Moves source tasks to tasks/archive/ via git mv with a Superseded-By marker; on any failure it rolls back all archived files and deletes the META. - Guardrails: Enforces a max bundle size of 6, warns on combined LOC over 400, halts on missing or duplicate IDs, detects stack conflicts, and supports Persian/Unicode slugs. - Use Case: A manager says "bundle tasks 12, 15, 20" for three small android-kotlin polish items; the bundle_tasks MCP tool generates one META task in tasks/backlog/ and archives the sources with full git history preserved. ## Quick Start Ask the agent to bundle tasks 12, 15, and 20 into a meta-task titled android-polish-bundle using the bundle_tasks MCP tool with dry_run enabled first.

Frequently Asked Questions about bundle-tasks

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

FAQPage Schema
How do I bundle multiple tasks into one meta-task?▼

Invoke the bundle_tasks MCP tool on mcp-context-server with task_ids, a title, and optional dry_run and force flags. It validates the IDs, discovers the next task ID, generates a META file in tasks/backlog/, and archives the sources automatically.

What is the maximum number of tasks I can bundle?▼

The maximum bundle size is 6 tasks, enforced by the MAX_BUNDLE_SIZE guardrail. Bundling more than 6 requires passing the force flag, and a warning is issued when combined source lines exceed 400.

Does bundling delete the original task files?▼

No. Source tasks are moved to tasks/archive/ via git mv and marked with a Superseded-By pointer to the META task. Full history remains reachable through git log --follow, and files are never purged until the META is completed.

What happens if archiving fails during a bundle?▼

The operation performs a transactional rollback: all previously archived files are restored to their original locations, the generated META file is deleted, and the tool exits with a clear error so no partial state remains.

Can I bundle tasks from different tech stacks together?▼

The tool auto-detects stacks such as android, react, fastapi, spring, ios, and go from task content. If conflicting stacks are detected, the bundle is blocked unless you explicitly pass the force flag.

When should I not use task bundling?▼

Avoid bundling for large refactors, tasks with conflicting files that would cause merge conflicts in a single diff, or more than 6 tasks without an explicit force override. Those cases are better executed as separate tasks.