Generate structured Task Specs and seed tasks by work type.
npx skills add https://github.com/beekeeper-lab/foundry --skill new-work
Please help me install this Agent Skill. Skill: new-work Source: https://github.com/beekeeper-lab/foundry/tree/main/.claude/skills/new-work Command: npx skills add https://github.com/beekeeper-lab/foundry --skill new-work
Single entry point for initiating any unit of work: bug fix, feature, chore, spike, or refactor. Collects the work type, goal, constraints, urgency, and affected areas, then creates a Task Spec, optionally drafts a BA artifact (user story for features, bug report for bugs), and seeds initial tasks with the appropriate dependency wave. This skill replaces the need for separate bug/feature/chore commands by routing through one consistent funnel that adapts its output based on the work type.
Invoke the New Work skill with a goal, type, and optional constraints to generate a Task Spec and seed initial tasks.
High-intent search queries and answers about installing and using this skill.
Create structured work items by defining the work type, goal, constraints, urgency, and affected areas. The system generates a task spec, drafts BA artifacts for features or bugs, and seeds initial tasks through appropriate dependency waves.
Yes, workflow orchestration routes bugs, features, chores, spikes, and refactors through one consistent funnel. It adapts outputs, determines involved personas, and seeds initial tasks with the appropriate dependency wave based on the work type.
A dependency wave structures seeded tasks by routing outputs through appropriate sequencing. When generating work items, the system determines involved personas and seeds initial tasks according to these dependency waves for structured project execution.
No, generating a work item uses a single entry point for bugs, features, chores, spikes, and refactors. The system adapts its output based on the work type, optionally drafting a bug report for bugs or a user story for features instead of requiring separate commands.
Seed initial tasks by invoking the command with a goal, type, and optional constraints. The system generates the task spec, drafts optional BA artifacts, and automatically seeds initial tasks through the appropriate dependency waves based on the work type.
Avoid single funnel work item generation when your project requires highly specialized artifact formats outside of standard task specs, user stories, or bug reports, or when your workflow demands isolated command routing for distinct work types.
productengineeredDefine v2.0 schema fields and constraints for epics, stories, and tasks.
0xharryriddleOrchestrate parallel subagents in waves using a dependency graph.
EmmittJMap thematic agent names to functional roles for task routing.
fwdarthGenerate Jira tasks with Prowler's standardized templates and component-based splitting.
