Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

spk-start-agent-surface

Étoiles1 373

Forks120

Mis à jour14 juin 2026 à 08:29

Choose the correct Spec Kitty workflow for Codex CLI, Claude Code, and supported slash-command or command-skill harnesses.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Priivacy-ai

Priivacy-ai/spec-kitty

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Autres occupations informatiquesProfessions informatiques et mathématiques·SOC 15-1299

SKILL.md

readonly

name	spk-start-agent-surface
description	Choose the correct Spec Kitty workflow for Codex CLI, Claude Code, and supported slash-command or command-skill harnesses.

spk-start-agent-surface

Use this skill when the question is about where Spec Kitty works, how commands or skills appear in a specific agent, or why behavior differs by surface.

Checks

Identify the surface: command line, Codex, Claude Code, slash-command host, or command-skill host.
Check whether slash commands, skills, and local filesystem access are available in that surface.
If commands are missing, route to spk-admin-setup-doctor.
If the user needs compatibility research, use the legacy spec-kitty-agent-surface-research skill when installed.

Guidance

Prefer local CLI workflows when the surface can read/write the repo.
Prefer command skills for slash-command execution.
Prefer spk-* skills for explanation, recovery, and orchestration.
Do not assume cloud-hosted agents can access local .kittify/, kitty-specs/, or .worktrees/ paths.

Plus depuis ce dépôt

même dépôt

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-start-agent-surface
description	Choose the correct Spec Kitty workflow for Codex CLI, Claude Code, and supported slash-command or command-skill harnesses.

spk-start-agent-surface

Use this skill when the question is about where Spec Kitty works, how commands or skills appear in a specific agent, or why behavior differs by surface.

Checks

Identify the surface: command line, Codex, Claude Code, slash-command host, or command-skill host.
Check whether slash commands, skills, and local filesystem access are available in that surface.
If commands are missing, route to spk-admin-setup-doctor.
If the user needs compatibility research, use the legacy spec-kitty-agent-surface-research skill when installed.

Guidance

Prefer local CLI workflows when the surface can read/write the repo.
Prefer command skills for slash-command execution.
Prefer spk-* skills for explanation, recovery, and orchestration.
Do not assume cloud-hosted agents can access local .kittify/, kitty-specs/, or .worktrees/ paths.