Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

spk-mission-specify

Estrellas1373

Forks120

Actualizado14 de junio de 2026, 08:29

Operate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Priivacy-ai

Priivacy-ai/spec-kitty

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	spk-mission-specify
description	Operate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria.

spk-mission-specify

Use this skill when creating or revising a mission specification.

Flow

Run or invoke /spec-kitty.specify for the feature.
Capture the user's concrete goal, constraints, non-goals, and success criteria.
Keep unresolved product decisions explicit instead of hiding them in plan details.
If terminology matters, route to spk-doctrine-glossary.
If governance affects scope, route to spk-doctrine-charter.

Output Standard

The spec should be good enough for /spec-kitty.plan to derive architecture and implementation strategy without inventing product intent. Work packages are authored by /spec-kitty.tasks.

Más de este repositorio

mismo repositorio

spec-kitty-bulk-edit-classification

Priivacy-ai/spec-kitty

Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request that touches the same identifier/path/key in many files. Also triggers on gate errors mentioning "change_mode", "occurrence_map.yaml", "Bulk Edit Gate: BLOCKED", or "Bulk Edit Review: Diff Compliance". Does NOT handle: line-level semantic refactors inside one file, adding a new feature that creates new identifiers without changing existing ones, or reviewing finished missions for fidelity.

2026-06-281.4k

spec-kitty-mission-review

Priivacy-ai/spec-kitty

Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review", "is this mission releasable", "final review before tagging", "cross-WP coverage audit". Does NOT handle: per-WP review during implementation (use spec-kitty-runtime-review), implement-review loop orchestration (use spec-kitty-implement-review), setup or repair (use spec-kitty-setup-doctor), or glossary maintenance (use spec-kitty-glossary-context).

2026-06-281.4k

spec-kitty-runtime-next

Priivacy-ai/spec-kitty

Drive the canonical spec-kitty next --mission <handle> control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the next task", "continue the workflow", "what step comes next". Does NOT handle: setup or repair requests, purely editorial glossary or doctrine maintenance, or direct code review.

2026-06-261.4k

spk-team-upsun-cli-sync

Priivacy-ai/spec-kitty

Point a local Spec Kitty CLI at Spec Kitty SaaS on Upsun (main or preview): set sync vars via use-upsun-env.sh, authenticate against Upsun Teamspace, check readiness, or drain local events.

2026-06-261.4k

spec-kitty-mission-system

Priivacy-ai/spec-kitty

Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 5-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior. Triggers: "what missions are available", "how do missions work", "which mission should I use", "explain the mission system", "what is a mission", "change the mission", "mission templates", "step contracts", "action index", "mission procedures". Does NOT handle: runtime loop advancement (use runtime-next), setup or repair (use setup-doctor), governance (use charter-doctrine), or glossary curation (use glossary-context).

2026-06-261.4k

spk-meta-skill-map

Priivacy-ai/spec-kitty

Discover the Spec Kitty 3.2.0 spk skill hierarchy, naming convention, legacy aliases, and the correct skill for a user intent.

2026-06-261.4k

name	spk-mission-specify
description	Operate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria.

spk-mission-specify

Use this skill when creating or revising a mission specification.

Flow

Run or invoke /spec-kitty.specify for the feature.
Capture the user's concrete goal, constraints, non-goals, and success criteria.
Keep unresolved product decisions explicit instead of hiding them in plan details.
If terminology matters, route to spk-doctrine-glossary.
If governance affects scope, route to spk-doctrine-charter.

Output Standard

The spec should be good enough for /spec-kitty.plan to derive architecture and implementation strategy without inventing product intent. Work packages are authored by /spec-kitty.tasks.