Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

spk-meta-skill-authoring

Estrelas1.373

Forks120

Atualizado14 de junho de 2026 às 08:29

Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Priivacy-ai

Priivacy-ai/spec-kitty

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	spk-meta-skill-authoring
description	Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.

spk-meta-skill-authoring

Use this skill when creating or revising a Spec Kitty skill.

Rules

Name public operating skills spk-<family>-<action-or-topic>.
Keep generated slash-command files separate from generated spec-kitty.<command> Agent Skills.
Preserve legacy spec-kitty-* skills when they remain useful aliases or detailed workflows.
Keep mission behavior in doctrine mission composition, not in skill prose.
Add tests when changing the public skill inventory.

Families

Use only established families unless a new family improves discovery: start, mission, run, gate, admin, team, doctrine, integrate, or meta.

Mais deste repositório

mesmo repositório

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-meta-skill-authoring
description	Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.

spk-meta-skill-authoring

Use this skill when creating or revising a Spec Kitty skill.

Rules

Name public operating skills spk-<family>-<action-or-topic>.
Keep generated slash-command files separate from generated spec-kitty.<command> Agent Skills.
Preserve legacy spec-kitty-* skills when they remain useful aliases or detailed workflows.
Keep mission behavior in doctrine mission composition, not in skill prose.
Add tests when changing the public skill inventory.

Families

Use only established families unless a new family improves discovery: start, mission, run, gate, admin, team, doctrine, integrate, or meta.