Seed Tasks

Decompose project objectives into assignable tasks with acceptance criteria and dependency graphs.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/foundry --skill seed-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Seed Tasks
Source: https://github.com/beekeeper-lab/foundry/tree/main/.claude/skills/seed-tasks
Command: npx skills add https://github.com/beekeeper-lab/foundry --skill seed-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes project objectives into actionable, assignable tasks so teams can plan, track, and execute work in predictable seed cycles.

Core Features & Use Cases

  • Maps goals to discrete tasks with assigned primary personas, acceptance criteria, and explicit dependencies.
  • Generates per-task markdown files, a dependency graph, and a workload summary for visibility.
  • Supports change-driven re-seeding when objectives evolve.

Quick Start

Assign project objectives and active personas, then run the seed-tasks process to generate tasks.

Frequently Asked Questions about Seed Tasks

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

FAQPage Schema
How do I decompose project objectives into actionable tasks for sprint planning?

Task decomposition breaks down project objectives into discrete, assignable tasks for a single seed cycle. It generates per-task markdown files with assigned primary personas, acceptance criteria, and dependency links for predictable execution.

What is a seed cycle in project management and when do I need to re-seed tasks?

A seed cycle is a single iteration of mapped project objectives producing discrete tasks with strict sequencing and non-circular dependencies. You need change-driven re-seeding when project objectives evolve and require new task decomposition.

What's the best way to visualize task dependencies for a project kickoff?

Visualizing task dependencies for project kickoff is best done using a generated Mermaid dependency graph. It maps explicit dependency links between discrete tasks, enforcing non-circular dependencies and strict sequencing for accurate workload visibility.

Can I assign specific personas to individual tasks during task decomposition?

Yes, task decomposition assigns a primary persona to each discrete task. Mapping goals to active personas ensures every generated task file has a clear owner and defined acceptance criteria for the seed cycle.

Does this task decomposition approach enforce limitations like one-task-per-cycle?

Yes, this approach enforces strict constraints including one-task-per-cycle, non-circular dependencies, and strict sequencing. These limitations ensure predictable workload tracking and prevent circular blocking during sprint planning.