4K skills · sorted by relevance
Measures implementation shortfall with paper portfolio comparison, delay cost attribution, and execution quality assessment. Use when measuring implementation shortfall, analyzing execution quality, or attributing trading costs.
The English summary is being prepared. Showing the original description.
Task Breakdown Command. Breaks a feature into discrete, dependency-ordered implementation tasks from a PRD and tech spec. Creates a task list and individual task files with no approval prompt. When run inside the `/start-job` pipeline, return control to that orchestrator so it can invoke the implementation phase. When invoked standalone, stop after generating tasks and prompting for the next step. Use when the user says "break this down into tasks", "create tasks", "task breakdown", or after the tech spec is complete and the user wants to plan implementation.
The English summary is being prepared. Showing the original description.
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
The English summary is being prepared. Showing the original description.
Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.
The English summary is being prepared. Showing the original description.
Creates accurate frontend implementations from visual references while maintaining design consistency. Use when user provides Figma URLs, screenshots, design images, requests visual implementation from reference, or asks to build UI matching a design. Automatically checks existing design intent patterns before implementation.
The English summary is being prepared. Showing the original description.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
The English summary is being prepared. Showing the original description.
Translate designs and UI requirements into robust, extensible implementations. Apply when converting designs to code, implementing components, fixing broken UI, or handling responsive layouts.
The English summary is being prepared. Showing the original description.
Turns a structured-autonomy PR plan (plans/{feature}/plan.md) into copy-paste-ready implementation documentation with complete code for every step, saved as implementation.md. Use after a plan exists and before implementation, when each step needs fully specified changes.
The English summary is being prepared. Showing the original description.
Use this skill for critical code review that focuses on whether the code actually works correctly and achieves the expected results - not just whether it matches a design document. This skill assumes designs can be wrong, finds bugs the design didn't anticipate, and verifies end-to-end correctness. Triggers include "critical code review", "deep code review", "verify this implementation works", "find bugs in this code", or reviewing implementation against requirements. NOTE - Security review is OUT OF SCOPE; use a dedicated security review skill for that purpose.
The English summary is being prepared. Showing the original description.
Load for Senior CTO critique, architectural audit, risk review, sequencing correction, or refinement of an existing implementation-plan triad; edits the requested plan/context/tasks in place without creating a worktree or review file. Not for open-ended CTO advice, product implementation, or implementation workspace setup.
The English summary is being prepared. Showing the original description.
Solution architect that creates implementation blueprints before building. Use when: (1) "architect this", "design a solution", "blueprint for", (2) Taking a task from the audit report and need an implementation plan, (3) "how should I build this?", "plan before building", (4) Before any non-trivial implementation. Reads from system/audit-report.md. Outputs to system/blueprints/.
The English summary is being prepared. Showing the original description.
実装設計エージェント - AIエージェントがコーディング可能な詳細実装仕様を生成。ドメインサービス・リポジトリ・値オブジェクト・例外マッピングのメソッドシグネチャと実装詳細を策定。/design-implementation [対象パス] で呼び出し。
The English summary is being prepared. Showing the original description.
Interactive Flutter Widget implementation assistant that guides you through widget implementation decisions by asking structured questions about state management, widget type (screen/component), and state sharing. Use this skill when you need help determining the appropriate Flutter widget architecture for your implementation.
The English summary is being prepared. Showing the original description.
Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "spec sanity check", "spec readiness gate", "spec consistency check". Output: docs/reviews/YYYY-MM-DD-<slug>-spec-crosscheck.md.
The English summary is being prepared. Showing the original description.
在用户已经完成一次 implementation 工作后，把项目里的 implementation plan + git diff/log 渲染成一份单文件 HTML 实施报告。报告包含 TL;DR、风险概览、架构图（mermaid）、Before/After 数据流、决策记录卡片、风险清单。用于开会前快速对齐团队、向 reviewer 解释设计决策、归档实施叙事。当用户说"生成实施报告"、"impl-explain"、"explain implementation"、"展示这次实施方案"、"做一份 HTML 实施总结"时调用本 skill。
The English summary is being prepared. Showing the original description.
Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.
Carry out an existing implementation plan in one session, task by task. Verify each step with tests, record progress and decisions in a file, and finish with a review of all changes on the branch.
Carry out an implementation plan by assigning each task to a separate agent, then reviewing specification compliance and code quality. Keep progress in files and review the complete set of changes after all tasks are finished.
Requests a code review from a separate agent after implementation or before merging. It provides the change summary, requirements, and commit range, then guides follow-up work according to the severity of the findings.
Turn an existing discussion and codebase knowledge into a specification, then publish it to the project's issue tracker. Organize the problem, user needs, implementation decisions, testing approach, and work excluded from scope.
Turn recurring work or life activities into workflow specifications through focused questions with recommended answers. Clarify triggers, human review, and decision summaries so an implementation agent can build the workflow without further questions.
Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.
Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.
Implement and review security measures in Quarkus applications. Covers sign-in, access permissions, input validation, password hashing, secret storage, request limits, audit logs, and checks for known vulnerabilities in dependencies, with implementation and configuration examples.