23 个 · 按相关度排序
Turn implementation plan phases into GitHub Issues with structured titles, descriptions, and labels. Check existing issues first, then create or update one issue per phase using feature or chore templates where available.
中文简介正在准备中。当前显示英语简介。
Turn feature requests, refactoring work, package upgrades, or infrastructure changes into structured Markdown implementation plans. Each plan defines concrete tasks, dependencies, affected files, and validation criteria for execution by AI agents or people.
中文简介正在准备中。当前显示英语简介。
Turn a feature requirements document into a detailed Markdown implementation plan following Epoch’s monorepo structure. Cover frontend components, APIs, database design, security, performance, and deployment, with Mermaid diagrams showing system architecture and data relationships.
中文简介正在准备中。当前显示英语简介。
Plan international hiring by comparing an employer of record, a provider that employs staff locally, with a local entity. Prepare stakeholder questions, draft local counsel briefing requests, and track unresolved tasks across sessions.
中文简介正在准备中。当前显示英语简介。
Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.
中文简介正在准备中。当前显示原文说明。
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
中文简介正在准备中。当前显示原文说明。
Guides conversion of gap analysis findings into phased implementation plans with milestones and risk-based prioritisation. Activate when building compliance programmes or allocating privacy budgets. Keywords: remediation roadmap, implementation plan, phased approach, prioritisation.
中文简介正在准备中。当前显示原文说明。
Use when you write the `plan` section of an analiz report - steps that pin files, signatures, tests and verify commands, nothing more
中文简介正在准备中。当前显示原文说明。
Writes a detailed, executable implementation plan from an approved design or multi-step requirement, including exact files, interfaces, tests, commands, checkpoints, and rollback considerations. Use before touching code for a substantial feature, migration, refactor, or cross-cutting change. Not for a one-file bounded fix or for executing a plan that already exists.
中文简介正在准备中。当前显示原文说明。
Validate whether an implementation plan can achieve its stated outcome before execution. Use to check requirement coverage, task contracts, dependencies, data/artifact flow, testability, ownership, impact coverage, and executable ordering without checking whether implementation already exists.
中文简介正在准备中。当前显示原文说明。
Turns a feature request into a full implementation-plan requirements document matching docs/plan/_TEMPLATE.md. Use when the user asks for requirements, a spec, an implementation plan, or wants to flesh out a feature before building. Also use for /requirements or "write requirements for X".
中文简介正在准备中。当前显示原文说明。
Creates structured multi-file implementation plans before build. Scope-aware: trivial tasks exit early, simple tasks get fast plans, complex tasks get full research + phase files + validation. Enforces Gate 1. Activated by /mk:plan or /mk:cook. NOT for ticket complexity analysis against an existing codebase (see mk:planning-engine); NOT for CEO-level scope review of existing plans (see mk:plan-ceo-review).
中文简介正在准备中。当前显示原文说明。
Codex adapter for Garry Tan's full gstack methodology across CEO/product pressure, CTO architecture, design, engineering, QA, security, shipping, documentation, and retrospectives. Use when the 总控/CEO or 架构/CTO role needs gstack method routing, implementation-plan hardening, or the user says gstack should help a role.
中文简介正在准备中。当前显示原文说明。
Load when the user asks to create, find, update, assign, label, prioritize, transition, or organize ISLAMU Event issues/cycles/modules in Plane via MCP; not for local todo lists or implementation-plan markdown.
中文简介正在准备中。当前显示原文说明。
Load when the user asks for CTO advice on feature strategy, architecture direction, build-vs-buy, infrastructure, market positioning, roadmap, self-hosting, cost, or organizational tradeoffs; not for reviewing an existing implementation-plan workstream.
中文简介正在准备中。当前显示原文说明。
Load when asked to create, update, re-baseline, or continue a repository-grounded implementation/technical/refactor plan and its `dev/active/<task>` plan/context/tasks files; not for a product PRD, informal advice, or reviewing an already-written plan.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus their focus areas, the document-to-model and design-build-test→model-analyze-build shifts, model formalisms/provenance, governance and access control of the authoritative source of truth, and the coordinate→plan→pilot→sustain rollout. A vision-and-policy strategy, deliberately non-prescriptive. Does NOT provide a how-to method, tool tutorials, MBSE/SysML mechanics, or implementation-plan content; thin on metrics, acquisition-policy detail, and step-by-step procedure. Excludes the CAC-gated Digital Engineering Body of Knowledge (DEBoK).
中文简介正在准备中。当前显示原文说明。
設計ドキュメントに基づいて実装計画を生成します。ScalarDB特有のスキーマ定義、トランザクション実装、統合テストを含む実装可能なタスク指示書を作成し、フェーズ別の実装ロードマップを提供します。
中文简介正在准备中。当前显示原文说明。
Plan which model tier handles which work BEFORE execution begins — a high-cognition model deeply understands the problem, lays the foundations, then emits a modular plan assigning each module the cheapest tier that can safely execute it, with escalation tripwires and one-way-door protection. Advisory only: it announces "next module → tier X / model Y" at each boundary and the HUMAN switches models — harnesses like Cursor cannot switch mid-run. Load when the user asks which model to use, wants a model plan, model tiers, model-tier routing, assign models to tasks or modules, says "cheap model got stuck", "which model for this task", "cost-efficient model choice", or when implementation-plan / problem-to-plan need a model: tier column. NOT dynamic-routing (plan-path selection after failure) — this skill assigns cognition tiers to work.
中文简介正在准备中。当前显示原文说明。
Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.
中文简介正在准备中。当前显示原文说明。
Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
中文简介正在准备中。当前显示原文说明。
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
中文简介正在准备中。当前显示原文说明。