spk-mission-tasks

Converts implementation plans into reviewable tasks and work packages for Spec Kitty workflows.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-mission-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-mission-tasks
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-mission-tasks
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-mission-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a high-level plan into executable work often produces vague, oversized tasks that agents and reviewers cannot act on independently. This Skill structures plan-to-task conversion so every work package has clear scope, dependencies, and verification criteria.

Core Features & Use Cases

  • Task Generation: Runs the default /spec-kitty.tasks flow to convert a plan into executable tasks.
  • Staged Work-Package Authoring: Uses /spec-kitty.tasks-outline, /spec-kitty.tasks-packages, and /spec-kitty.tasks-finalize for incremental package slicing and finalization.
  • Reviewable Boundaries: Enforces that each work package defines scope, dependencies, verification, and expected files or systems, and splits oversized packages before runtime execution.
  • Use Case: After finishing a feature plan, generate work packages that reviewers can approve or reject independently before assigning them to parallel agents in isolated git worktrees.

Quick Start

Ask the agent to convert the current Spec Kitty plan into reviewable work packages using the tasks workflow.

Frequently Asked Questions about spk-mission-tasks

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

FAQPage Schema
How do I convert a Spec Kitty plan into tasks?

Run the default `/spec-kitty.tasks` command to convert a plan into executable tasks. For staged authoring, use `/spec-kitty.tasks-outline`, `/spec-kitty.tasks-packages`, and `/spec-kitty.tasks-finalize` in sequence.

How do I split work packages in Spec Kitty?

Use the staged work-package authoring flow with `/spec-kitty.tasks-outline` and `/spec-kitty.tasks-packages` to slice the plan, then finalize with `/spec-kitty.tasks-finalize`. Split any package too broad for implementation or review lanes before runtime execution.

What makes a work package reviewable in Spec Kitty?

A reviewable work package has a clear scope, declared dependencies, verification criteria, and expected files or systems. A reviewer should be able to approve or reject each package independently without referencing other packages.

When should I use staged task authoring instead of the default tasks command?

Use staged authoring with the outline, packages, and finalize commands when work-package authoring is enabled and the plan is large enough to need incremental slicing. The default `/spec-kitty.tasks` path suits straightforward plan-to-task conversion.

What happens if a work package is too broad for review lanes?

Oversized packages should be split before runtime execution begins. Keeping packages narrow ensures they fit implementation and review lanes and remain independently approvable.