dev-task-builder

To generate GitHub Issues from feature specification documents, this Skill analyzes your functional requirements and E2E scenarios to slice work into issue-ready Markdown summaries with execution order and dependencies. It maps functional requirements directly to E2E test coverage for traceability.

E2E-driven task slicing is a planning method that splits feature specifications into buildable work increments. Each task slice delivers an observable feature increment verifiable by an end-to-end test, ensuring that development tasks align directly with user value and E2E scenarios.

Mapping dependencies and execution order for a SaaS module involves analyzing data models and security rules within your specification. This Skill identifies critical paths, orders tasks sequentially, and validates FR-to-E2E coverage to produce a structured execution plan.

Yes, you can analyze local feature spec directories for task planning without external dependencies. The Skill operates entirely on local specification documents within the docs/specs/ folder, requiring no additional libraries or external platform connections to generate execution guidance.

Yes, this task planning approach validates functional requirement coverage against E2E scenarios. It cross-references your functional requirements with E2E test cases to ensure complete traceability, highlighting any gaps in coverage before generating the issue-ready task list.

A limitation when transforming complex feature specifications into development task plans is that the Skill requires a strictly structured docs/specs/ directory. It relies on well-defined functional requirements and data models, meaning poorly structured or incomplete specification documents will yield inaccurate dependency mapping.