Individual skill

spk-mission-tasks

Operate Spec Kitty task and work-package authoring, including tasks outline, package slicing, and finalization.

src/charter/offering/skills/spk-mission-tasks/SKILL.md

Read pinned source

Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,717
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
gemini-cli Repository topic
spec-driven-development Repository topic
cursor-agent Repository topic
github-copilot Repository topic
windsurf Repository topic
ai-coding-workflow Repository topic
ai-development-dashboard Repository topic
ai-progress-tracking Repository topic
coding-agent-orchestration Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 800 bytes

Read excerpt


# spk-mission-tasks

Use this skill when converting a plan into executable tasks or work packages.

## Flow

1. Use `/spec-kitty.tasks` for the default path.
2. Use `/spec-kitty.tasks-outline`, `/spec-kitty.tasks-packages`, and
   `/spec-kitty.tasks-finalize` when staged work-package authoring is enabled.
3. Keep package boundaries reviewable: each WP should have a clear scope,
   dependencies, verification, and expected files or systems.
4. If WPs are too broad for implementation/review lanes, split before runtime
   execution begins.