
Verify architecture and design documents against code implementation; produce an Architecture Compliance Report when implementation diverges from ADR or design decisions.
Perform post-task traceback, drift detection, and top-down recalibration to keep planning (goals, requirements, milestones, roadmap) aligned with task execution.
Assess alignment gaps between code changes and required documentation updates.
Assess SSOT integrity with intent-first methodology and produce conflict matrix with canonical source mapping.
Audit documentation governance in read-only mode and produce a unified report with prioritized actions and explicit skill routing.
Single-step governance executor — reads plan-next routing output, executes the highest-priority action, and emits a continuation signal for /loop-driven autopilot.
Iteratively review changes, run automated tests, and apply targeted fixes until issues are resolved (or a stop condition is reached).
Bootstrap or adapt project docs using project-documentation-template. Core goal - produce structured lifecycle documentation aligned with enterprise template. Initialize (empty) or Adjust (non-empty); repeatable; strict kebab-case naming.
--- name: breakdown-tasks description: Break a design document into an executable task list with dependencies, acceptance criteria, and assignee or AI execution hints. Use when design is approved and you need an implementation plan. description_zh: 将设计文档拆解为可执行任务列表:依赖、验收标准、负责人或 AI 执行提示。 tags: [writing, documentation, workflow] version: 3.0.0 license: MIT recommended_scope: both metadata: author: ai-cortex triggers: [breakdown tasks, task breakdown, implementation plan, tasks from design] input_
Govern skill inventory through output-contract and acceptance-criteria checks, lifecycle assignment, and overlap detection. Core goal — produce verifiable status and normalized documentation for all skills in repository.
Review given file/dir/repo for current-state code organization: module boundaries, design patterns, cross-module dependencies, tech debt, and interface stability. Scope-only atomic skill; output is a findings list.
--- name: design-solution description: Produce a validated design document from requirements (architecture, components, data flow, trade-offs) with no implementation. Use when requirements are clear and you need a single source of truth for downstream task breakdown. description_zh: 从需求产出验证过的设计文档(架构、组件、数据流、权衡);不含实现;用于下游任务拆解。 tags: [writing, documentation] version: 3.0.0 license: MIT recommended_scope: both metadata: author: ai-cortex evolution: sources: - name: "design-solution"
Identify missing skills and recommend installations from AI Cortex or public skill catalogs. Core goal - provide top 1-3 skill matches with install commands for Agent capability gaps. Use when discovering capabilities or suggesting skills to fill gaps.
Install rules from source repo into Cursor or Trae IDE with explicit confirmation and conflict detection. Core goal - install rules to editor destinations with user approval before any write.
Generate lean, high-density README. Sections pruned by value threshold — not fixed count. Primary goal — reader knows what the project is, where to look, and how to use it within 30 seconds.
--- name: investigate-root-cause description: Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". description_zh: 系统性根因调试:investigate → analyze → hypothesize → implement。铁律:无根因不修复。适用于报错、异常行为、故障排查。 tags: [workflow, optimization] version: 1.0.0 license: MIT recommended_scope: both
From the main repo, scan all active worktrees, select and batch-merge branches into main, push, and clean up together.
Review code for architecture: module and layer boundaries, dependency direction, single responsibility, cyclic dependencies, interface stability, and coupling. Cognitive-only atomic skill; output is a findings list.
Review ORM usage patterns for N+1 queries, connection management, migration safety, transaction handling, and query efficiency. Library-level atomic skill; output is a findings list.
Review Java code for language and runtime conventions: concurrency, exceptions, try-with-resources, API versioning, collections and Streams, NIO, and testability. Language-only atomic skill; output is a findings list.
Review React code for component design, hooks correctness, state management, rendering performance, and accessibility. Framework-only atomic skill; output is a findings list.
# 技能规范 (Skill Specification) 状态:必选 版本:2.7.5 范围:`skills/` 下所有文件。 **变更日志**: - v2.7.5 (2026-03-22):§4 新增文档制品原则 — YAGNI、DRY、简洁适用于产出 document-artifact 的技能 - v2.7.4 (2026-03-22):内容与结构精简 — 变更日志归档;§1 命名收敛;§3.1 重要性缩句;§4 去重、§4.4 合并;§5 与 §9 合并;§7.1 流程合并 - v2.7.3 (2026-03-22):YAGNI/DRY 优化 — 精简演进元数据、§8.5 D/C 模式;合并重复定义;修正示例技能名与路径 - v2.7.2 (2026-03-21):移除 `related_skills` 元数据;技能关系改由 prose 中的 Handoff Point 与 Scope Boundaries 说明 - v2.7.0 (2026-03-16):新增 Divergent(探索)与 Convergent(决策/制品)两阶段模型 - v2.6.0 (2026
Sync project documentation after release. Reads all docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS. Use when asked to "update the docs", "sync documentation", or "post-ship docs".
Audit repository structure in one pass — detect misplaced files, naming inconsistencies, empty directories, and stale artifacts; produce a prioritized tidy report; optionally apply safe, reversible changes.
Publish a NATS message conforming to a cross-team contract, using NATS MCP tools. Authors the contract on first use if missing. Reads project-level cache (.cortex/nats.yaml) to avoid re-prompting basics across sessions.
Review code for performance: complexity, database/query efficiency, I/O and network cost, memory and allocation behavior, concurrency contention, caching, and latency/throughput regressions. Cognitive-only atomic skill; output is a findings list.
--- name: analyze-requirements description: Transform vague intent or incomplete requirements into validated, testable requirements through diagnostic state progression and structured dialogue. Use when user has an idea, feature request, problem statement, or existing requirements document that needs clarification or validation before design or implementation. description_zh: 通过诊断状态推进与结构化对话,将模糊意图或不完整需求转为可验证、可测试的需求。 tags: [writing, documentation] version: 3.0.0 license: MIT recommended_scope: bot
Analyze governance state and suggest next actions from existing docs; read-only — never executes downstream skills.
Align the product or work backlog with the current strategy, goals, and roadmap. Analyze backlog items, identify misaligned or orphan work, and propose concrete changes (adds, cuts, reprioritization) so backlog clearly supports strategic outcomes.
Assess documentation link graph health including broken links, orphan docs, cycles, and deep chains.
Discover and propose project-specific artifact norms (paths, naming, lifecycle) from existing docs structure without writing norms files.
Orchestrate comprehensive code reviews by running scope, language, framework, library, and cognitive review skills in sequence, then aggregate findings into a unified report.
Review code for security: injection, sensitive data, auth, dependencies, config, and crypto. Atomic skill; output is a findings list.
Assess documentation core health in one pass — artifact norms compliance, layer readiness scoring, and minimum fill plan.
Review Vue 3 code for Composition API, reactivity, components, state (Pinia), routing, and performance. Framework-only atomic skill; output is a findings list.
Warn before destructive commands. Checks Bash commands for rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar patterns. User can override each warning. Use when touching prod, debugging live systems, or in shared environments.
Discover and execute repository test commands safely with evidence-based command selection and safety guardrails.
Archive a completed milestone by generating a snapshot summary, folding the roadmap stage, and removing the stale tasks directory.
From the main repo on the main branch, scan all linked worktrees, let the user multi-select, then merge --no-ff + push them sequentially and clean up the succeeded ones together.
Define the long-term future the project aims to create. Answers what future we are building; produces a vision statement aligned with mission, persisted to docs.
Audit and refactor existing SKILLs to meet spec compliance and LLM best practices. Use when improving drafts, fixing quality, or aligning to spec.
Review Go code for language and runtime conventions: concurrency, context usage, error handling, resource management, API stability, type semantics, and testability. Language-only atomic skill; output is a findings list.
Review Python code for language and runtime conventions: type hints, exceptions, async/await, context managers, dependencies, and testability. Language-only atomic skill; output is a findings list.
Single-step governance executor — reads plan-next routing output, executes the highest-priority action, and emits a continuation signal for /loop-driven autopilot.
Derive a strategic roadmap from goals using milestone checkpoints, strategic bets, success metrics, and promotion criteria. Produces a decision-grade roadmap document.
Define the single most important metric representing the core value delivered to users. Produces North Star Metric with rationale, optional supporting metrics, and anti-pattern examples; persisted to docs.
Create high-quality git commits with clear messages and logical scope. Core goal - produce reviewable commits following Conventional Commits format with pre-commit quality checks.
Create or update docs/ARTIFACT_NORMS.md from an approved proposal and establish project docs norms as canonical rules.
Define the fundamental purpose of a project or organization. Answers why the project exists; produces a single mission statement persisted to docs.
Convert text with private context or internal dependencies into generic, unbiased expressions that are standalone and reusable. Core goal - produce decontextualized text that preserves logic while removing organizational identifiers. Use for project handoff, open-source prep, methodology abstraction, cross-team sharing.
Write or revise AGENTS.md per embedded output contract to establish project identity, authoritative sources, and behavioral expectations. Use when creating Agent entry for new projects, auditing existing AGENTS.md, or adopting the AI Cortex entry format.
Force a clean re-score of every backlog item with four frameworks (RICE, WSJF, MoSCoW, ICE) in parallel — ignores any existing priority, auto-detects multi-file or single-file backlog layouts, surfaces framework disagreements, and captures the user's final decision with rationale.
GitHub Actions YAML with embedded output contract: security-first, minimal permissions, version pinning. For CI, release, PR checks. Differs from generic templates by spec compliance and auditability.
Define 3–5 long-term strategic goals that move the project toward the vision and North Star. Produces a goals document aligned with mission, vision, and NSM; persisted to docs.
From inside a linked worktree, deliver the current feature branch into main — merge with --no-ff, push, and optionally clean up the worktree, all without leaving CWD.
Iteratively review changes, run automated tests, and apply targeted fixes until issues are resolved (or a stop condition is reached).
Promote prioritized backlog items into the roadmap's Now/Next/Later tiers based on strategic_goal capacity allocation and priority scores. Event-driven (not calendar-driven).
Review PHP code for language and runtime conventions: strict types, error handling, resource management, PSR standards, namespaces, null safety, generators, and testability. Language-only atomic skill; output is a findings list.
Derive 3–5 strategic pillars (high-level themes) from vision and North Star that structure and guide strategic goals and roadmap. Produces a strategic pillars document; persisted to docs.
Orchestrator skill — sequence atomic review-* skills (scope → language → framework → library → cognitive) and aggregate findings into a unified report.
Review .NET (C#/F#) code for language and runtime conventions: async/await, nullable, API versioning, IDisposable, LINQ, and testability. Language-only atomic skill; output is a findings list.
Review an existing requirements document for quality: problem clarity, testable needs, constraint inventory, scope boundedness, requirement IDs, and open questions. Evaluative atomic skill; output is a findings list.
Review PowerShell code for language and runtime conventions: advanced functions, parameter design, error handling, object pipeline behavior, compatibility, and testability. Language-only atomic skill; output is a findings list.
Review code for testing: test existence, coverage adequacy, test quality and structure, edge-case and error-path coverage, and test maintainability. Cognitive-only atomic skill; output is a findings list.
Review SQL and query code for injection risk, parameterization, indexing and performance, transactions, NULL and constraints, and dialect portability. Language-only atomic skill; output is a findings list.
Generate an LLM agent test suite (golden cases, mock-LLM unit tests, evaluator harness) from an agent implementation and its agent-test contract. Use when an agent has no tests, or a contract exists but the test code is missing.
Capture requirements, bugs, or issues from free-form input into structured, persistent artifacts. Use when user wants to record a work item quickly without deep validation.
Review TypeScript/JavaScript code for type safety, async patterns, error handling, and module design. Atomic skill; output is a findings list.
Drain pending NATS messages from a producer contract via NATS MCP tools (default batch / drain-style). Applies Tolerant Reader semantics and per-message ack/nak/term, returning aggregated stats. Reads project-level cache (.cortex/nats.yaml) to avoid re-prompting.
Review only git diff for impact, regression, correctness, compatibility, and side effects. Scope-only atomic skill; output is a findings list for aggregation.
Detect drift between project work-item manifest files and the physical artifacts they register (requirements / designs / tasks / PRs). Advisory-only in v1.0.0 — reports drift, does not auto-write.
After code changes, auto-detect the project's build system and local deployment method for a given directory, then build the project and restart its locally-deployed environment (Docker Compose / systemd / process manager). Never assumes — asks only when detection is ambiguous. Caches detected commands per project in .cortex/redeploy-local.yaml; re-invocations on the same project skip re-scanning until signal files change, the cache expires (30 days), or the skill version bumps.