development_execution

Extracts sprint tasks from documents and delegates them to swarm tools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ukrsite/kiro-workflows --skill development-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development_execution
Source: https://github.com/ukrsite/kiro-workflows/tree/main/skills/sdlc/development_execution
Command: npx skills add https://github.com/ukrsite/kiro-workflows --skill development-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts sprint task items from planning documents and task trackers and delegates execution to swarm tools, enabling teams to avoid manual orchestration and handoffs.

Core Features & Use Cases

  • Task extraction: parse sprint plans and task-tracker files to build a structured list of TK-XXX tasks in topological order.
  • Delegation to swarm tools: pass the complete task list to swarm_tool for autonomous execution without generating solutions or code.
  • Audit and guardrails: maintain per-run audit logs and enforce safety constraints.

Quick Start

Provide a sprint plan document and the skill will extract tasks and delegate to swarm_tool.

Frequently Asked Questions about development_execution

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

FAQPage Schema
How do I extract sprint tasks from planning documents for automated execution?

Sprint task extraction parses planning documents and task trackers to identify TK-XXX items, structuring them in topological order while preserving dependencies. It delegates the full list to swarm tools for autonomous execution without generating code.

Can I delegate sprint tasks to swarm tools without writing code manually?

Delegating sprint tasks to swarm tools requires no manual code generation. The skill passes the extracted task list to swarm_tool for autonomous execution, applying strict guardrails to prevent generating solutions or code.

What's the best way to orchestrate a swarm for a sprint plan with task dependencies?

Orchestrating a swarm for a sprint plan requires extracting TK-XXX tasks in topological order to preserve dependencies. The structured list is then delegated to swarm tools for execution with strict audit-logging guardrails.

Does sprint task delegation maintain audit logs for delegated execution runs?

Sprint task delegation maintains per-run audit logs for delegated execution. It enforces safety constraints and audit-logging guardrails throughout the extraction and delegation process to track autonomous swarm execution.

Why does the swarm delegation skill avoid generating solutions or code directly?

Swarm delegation avoids generating solutions or code directly to enforce strict safety guardrails during execution. It delegates tasks to swarm tools, ensuring autonomous completion while maintaining per-run audit logs.

When do I need topological task ordering for sprint plan delegation?

Topological task ordering for sprint plan delegation is needed when planning documents contain TK-XXX identifiers with dependencies. This ensures swarm tools execute tasks in the correct sequence, preserving task order and constraints.