campaign-status
Check active campaign status. Use when: cross-platform execution history, performance metrics, pending approvals.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Check active campaign status. Use when: cross-platform execution history, performance metrics, pending approvals.
Classify a task or feature as quick, standard, or thorough so the rest of the pipeline (budget sizing, model routing, review depth) can right-size itself. Used by /ck:sketch to default the kit's complexity, by /ck:map to assign task depth, and by /ck:make for per-task budgets. Also invoked by the ck:complexity agent with the haiku model. Trigger phrases: "how complex", "what depth", "pick a depth", "classify this task".
Integrate documentation work with Agile product development by making docs visible in sprint planning, release trains, definitions of done, review timing, and retrospective improvement. Use when docs are missing from scrum boards, stories, acceptance criteria, release planning, or cross-team work, or when writers need a lightweight process for documentation inside Agile teams.
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.
Use when entering a project for the first time, or when the user asks to establish shared language, define domain terms, or create a project glossary.
基于 Git Worktree 的任务隔离工作流:每个开发任务在独立 worktree 中执行, 确保主工作区干净、并行任务互不干扰,完成后结构化决策合并/PR/保留/丢弃。 与 parallel-execution 的 worktree 基础设施互补,本 skill 聚焦任务级隔离策略。
Use when executing an approved Krypton plan, GOAL.md, or implementation plan that already defines intent, ownership, contract, cutover, task boundaries, and acceptance evidence. Use for main-agent execution with explorer, plan-reviewer, reviewer, maintainer, or verifier gates.
Use when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding. Use especially when wrong ownership, duplicate paths, stale contracts, weak evidence, or unclear cutover would make plausible agent work dangerous.
Use the OpenProject Codex plugin to inspect and manage work in Codex through the OpenProject API.
Use when a Codex execution should report progress, artifacts, blockers, or completion state back to OrgX during a live task.