Sponsored by

Find leads on Reddit on auto pilot

Agent skills
agentic-coding

Topic: agentic-coding

2,023 skills in this topic.

spec-kitty-charter-doctrine Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter", "sync charter", "use doctrine", "set up governance", "charter status", "extract governance config", "load doctrine", "agent profile", "DoctrineService", "action index". Does NOT handle: generic spec writing not tied to governance, direct runtime loop advancement, setup/repair diagnostics, or editorial glossary maintenance.
Priivacy-ai/spec-kitty 1,051
spec-kitty-git-workflow Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git workflow", "merge workflow", "rebase WPs", "worktree cleanup", "safe commit". Does NOT handle: runtime loop advancement (use runtime-next), setup or repair (use setup-doctor), mission selection (use mission-system).
Priivacy-ai/spec-kitty 1,051
spec-kitty-glossary-context Curate and apply canonical terminology across Spec Kitty missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts", "resolve ambiguity", "review terminology consistency". Does NOT handle: runtime loop advancement, setup or repair requests, agent configuration, or direct code implementation tasks.
Priivacy-ai/spec-kitty 1,051
spec-kitty-implement-review Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop", "orchestrate WP implementation", "dispatch agents for WPs", "coordinate implement and review", "sprint through WPs". Does NOT handle: specify/plan/tasks phases, setup or repair, glossary maintenance, or direct code editing by the orchestrator.
Priivacy-ai/spec-kitty 1,051
spec-kitty-mission-review 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).
Priivacy-ai/spec-kitty 1,051
spec-kitty-mission-system 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).
Priivacy-ai/spec-kitty 1,051
spec-kitty-orchestrator-api-operator Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool", "orchestrator contract", "external automation". Does NOT handle: host-internal lane mutation (use the host CLI directly), runtime loop advancement (use spec-kitty next), mission sequencing logic (the mission state machine owns that), or setup/repair diagnostics.
Priivacy-ai/spec-kitty 1,051
spec-kitty-runtime-next Drive the canonical spec-kitty next --agent <name> 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.
Priivacy-ai/spec-kitty 1,051
spec-kitty-runtime-review Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only repair requests, direct implementation work, editorial glossary maintenance, or runtime loop advancement.
Priivacy-ai/spec-kitty 1,051
spec-kitty-setup-doctor Install, verify, and recover the modern Spec Kitty 2.0.11+ operating surface. Triggers: "set up Spec Kitty", "skills missing", "next is blocked", "runtime is broken", "doctrine assets are missing", "my agent can't find the skills". Does NOT handle: generic coding questions with no Spec Kitty context, direct runtime loop advancement, or editorial glossary maintenance.
Priivacy-ai/spec-kitty 1,051
receiving-code-review 收到代码审查反馈后、实施建议之前使用，尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证，而非敷衍附和或盲目执行
jnMetaCode/superpowers-zh 771
using-git-worktrees 当需要开始与当前工作区隔离的功能开发或执行实现计划之前使用——创建具有智能目录选择和安全验证的隔离 git 工作树
jnMetaCode/superpowers-zh 771
mcp-builder MCP 服务器构建方法论 — 系统化构建生产级 MCP 工具，让 AI 助手连接外部能力
jnMetaCode/superpowers-zh 771
finishing-a-development-branch 当实现完成、所有测试通过、需要决定如何集成工作时使用——通过提供合并、PR 或清理等结构化选项来引导开发工作的收尾
jnMetaCode/superpowers-zh 771
executing-plans 当你有一份书面实现计划需要在单独的会话中执行，并设有审查检查点时使用
jnMetaCode/superpowers-zh 771
dispatching-parallel-agents 当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用
jnMetaCode/superpowers-zh 771
chinese-git-workflow 适配国内 Git 平台和团队习惯的工作流规范——Gitee、Coding、极狐 GitLab 全覆盖
jnMetaCode/superpowers-zh 771
chinese-documentation 中文技术文档写作规范——排版、术语、结构一步到位，告别机翻味
jnMetaCode/superpowers-zh 771
chinese-commit-conventions 中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
jnMetaCode/superpowers-zh 771
chinese-code-review 中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈
jnMetaCode/superpowers-zh 771
brainstorming 在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能或修改行为。在实现之前先探索用户意图、需求和设计。
jnMetaCode/superpowers-zh 771
requesting-code-review 完成任务、实现重要功能或合并前使用，用于验证工作成果是否符合要求
jnMetaCode/superpowers-zh 771
subagent-driven-development 当在当前会话中执行包含独立任务的实现计划时使用
jnMetaCode/superpowers-zh 771
systematic-debugging 遇到任何 bug、测试失败或异常行为时使用，在提出修复方案之前执行
jnMetaCode/superpowers-zh 771