After reviewing a contract, plan exactly what to push back on. I sort the issues into must-haves, nice-to-haves, and not-worth-fighting, write the exact wording you can paste into…
Obstruktionsverbot und gruppenuebergreifende Mehrheitsentscheidung prüfen wenn ablehnende Gruppen oder Klassen vorhanden sind. § 245 InsO § 27 StaRUG Cramdown.
Checklist-driven prompt to prepare a full Caravella release (changelogs, store metadata, version bump, tag)
Strategic and operational plans: OKR, quarterly, launch. Use when creating OKRs, quarterly plans, or launch plans.
Dual-critic review pass for a drafted plan. Runs DESIGN CRITIC and FEASIBILITY CRITIC agents in parallel against the plan YAML, then writes findings as critic_revisions on the…
Harshly critique strategic documents (validation reports, competitive analyses, business plans) to identify blind spots, challenge assumptions, expose weaknesses, and generate…
Darstellenden Teil des Insolvenzplans oder StaRUG-Plans vollständig und widerspruchsfrei verfassen. § 220 InsO § 6 StaRUG Darstellungspflichten.
Planbegleitenden Datenraum aufbauen und Dokumentenregister führen wenn alle Planbausteine belegbar sein muessen. §§ 218 229 InsO §§ 14 15 StaRUG Planunterlagen.
Plan-only dead-code audit: Knip baseline for unused files, exports, and deps, plus duplication, debug residue, suppressions, orphan assets, env drift. Deletes nothing.
Investigation Opus d'un plan en difficulté (bugs, blocages, effets nuls), dans une session Opus. Déclencher avec "/plan-debug" suivi du chemin du plan, "debug ce plan avec…
Audit dependencies for hallucinated or slopsquatted packages, supply-chain risk, and licensing/provenance gaps, then produce a phased remediation plan.
Use when issue-spotting a Chapter 11 plan and disclosure statement into a source-cited treatment table and issue list for attorney review, without concluding confirmability.
문서 작성을 위한 전용 플래닝 스킬. 다양한 소스 조사 → 구조화/정제 → 팩트체크 검증의 반복 루프로 문서 plan을 수립합니다.
Audit documentation against actual code behavior and plan corrections — no rewrites in this pass. Drift taxonomy (stale, missing, phantom, contradictory, onboarding-breaking,…
Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
Method clarity-driven planning workflow using zen-mcp tools (chat, planner, consensus). Phase 0 uses chat to judge if user provides clear implementation method.
Planning rules and plan template for drafting implementation plans. Invoked as /plan-draft for an ad-hoc planning session, or used by the planner sub-agent in the /feature…
Generate a structured engineering plan markdown for an idea, pre-filled with codebase facts (stack, dependencies, current critique score) from dragoon.json.
Plan a complete EU/DACH relocation timeline with dependency mapping between bureaucratic steps, deadline tracking, and country-specific procedure identification.
작업 계획서(docs/plans/*-plan.md)를 입력으로 받아 TODO를 병렬 실행하여 코드를 작성하는 스킬. 의존성 분석 → 배치 분할 → 병렬 executor → 배치 간 검증/자가수정 패턴으로 동작. 계획 기반 구현, 자동 코딩, TODO 실행, plan execution 요청 시 이 스킬을 사용할 것.
Use when deciding HOW to split work between a strong planner and cheaper executors — configuring subagent models, writing delegation prompts, running the plan-big/execute-small…
Batch execution with checkpoints. Trigger: When executing plans with batched tasks.
Expertise in executing finalized architectural plans. Use when the user asks to "implement the plan", "build the feature", or "execute the strategy".
Chain plan-review-autofix, plan-wrap-autofix, repo-sync, and task-handoff into one autonomous prep step before /build-phase. Required arg --plan
.
Plan a new feature with analysis, design, and implementation steps. Use when the user asks to plan a feature or run /plan-feature.
모든 지시를 수행하기 전에 반드시 "조사 -> 계획 -> 확인 -> 실행" 워크플로우를 따르는 스킬. 사용자의 지시를 받으면 바로 실행하지 않고, 먼저 프로젝트 파일과 코드 구조를 파악하고, 부족한 정보는 웹 검색으로 보충하고, 불명확한 점은 사용자에게 질문하여 확인한 뒤, 수행 계획을 세워 사용자의 승인을 받고 나서…
Use when a task needs an implementation plan that is iteratively created and stress-tested through review-and-revise cycles before implementation begins — catches blind spots,…
Break a scope or feature set into stories and tasks for sprint planning (Sofia Nakamura's workflow)
Plan garden activities using solar, lunar, and biodynamic calendars. Covers USDA hardiness zones, frost date calculation, equinox/solstice anchoring, synodic lunar cycle…
Use when a WORKSPACE's Plan (timeline) has gone stale (or has never been generated) and an agent must (re)derive its soft structure — bucket grouping + a suggested project layout…
Gerichtliche Verfahrensschritte für Insolvenzplan und StaRUG-Plan steuern von Einreichung bis Bestätigung. §§ 231 232 248 InsO Vorprüfung Bestätigung §§ 45 ff.
Gestaltenden Teil des Insolvenzplans mit konkreten Rechtsaenderungen Quoten und Vollstreckungsgrundlagen formulieren. § 221 InsO § 7 StaRUG Planwirkungen.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Abstimmungsgruppen nach InsO und Klassen nach StaRUG sachgerecht bilden um Planbestätigungsrisiken zu minimieren. §§ 222 223 InsO Gruppenbildung §§ 9 10 StaRUG Klassenbildung.
Build detailed implementation plans with file-level specificity, complexity estimates, and a docs-then-tests-then-code workflow.
Show all available Cycle ecosystem commands with descriptions and recommended flows. Use when the user asks for help, wants to know what commands are available, or says "what can…
Plan a hiking tour with trail selection by difficulty (SAC/UIAA), time estimation using Munter's formula, elevation analysis, and safety assessment.
Use when the user says "plan an idea", "pick an idea", "work on an idea", or wants to select a pending idea from pm-tool and enter plan mode with its full context.
コードベース調査 → 要件壁打ち → 設計書作成 → チェックリスト検証までの着手前設計スキル。実装には進まない。（デフォルト: CC Agent、--codex で codex CLI）
Parse and ingest pilot plans and hypotheses into structured data for downstream analysis. Use when needing to extract objectives, deliverables, timelines, or hypotheses from pilot…
Guide the creation of a new project plan.md through a structured conversation. Asks the right questions up front — stack, auth, data storage, async patterns, build tooling, UI —…
Vollständigen Insolvenzplan nach §§ 217 ff. InsO von Grund auf strukturieren. §§ 217 220 221 InsO Planarchitektur.
Integrierte Planrechnung aus GuV, Liquidität und Bilanz für Insolvenzplan, StaRUG oder Sanierungskonzept erstellen. §§ 220 229 InsO Finanzplanung § 14 StaRUG.
Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.
Plan phase — autonomously plan a no-PR issue into an ordered unit breakdown via the built-in Explore/Plan subagents, persist the plan to the issue, and apply dispatch:planned (no…
要件を分析し、実装可能な Issue に分解して Linear に登録します。 Trigger: plan, decompose, 要件分解, issue作成
Steuerliche und bilanzielle Folgen des Insolvenzplans oder StaRUG prüfen damit Planwirkungen nicht an Nebenwirkungen scheitern.
Erstes Mandatsgespräch strukturieren wenn Insolvenzplan oder StaRUG-Verfahren startet und kaum Unterlagen vorliegen. §§ 13 15a 17 InsO §§ 29 42 StaRUG Antragspflichten.
Audit an LLM-powered app for runaway-cost and quota-abuse exposure, then produce a phased guardrail plan.
计划锁定器。把修复计划、实现方案和 WP 规格锻造成 decision-complete 的可执行上游文档：真相先验、决策关死、接口对齐、测试层级一致、时序稳定。在 lead 的 Gate 1 与 Gate 2 之间，以及 task-arch 拆 WP 之前必须使用。
Use when scoping multi-session work that can't finish with quality in one chat (bulk generation ≥100 unit, multi-phase pipeline with human gates, external manual steps).
The exact five-part shape of PLAN.md, the one plan in flight at the repo root: title, catchy phrase, context, phases with Rationale/Data/Acceptance/Unknowns, and state.
Merge two overlapping plan documents into a single coherent plan. Identifies shared goals at different fidelity, resolves sequencing tensions, picks a spine, deletes subsumed…
Schlechterstellungsrisiken und Beschwerderisiken einzelner opponierender Beteiligter analysieren und Planverbesserungen vorschlagen. § 251 InsO § 64 StaRUG Minderheitenschutz.
Audit a Capacitor/React Native app for App Store and Google Play submission readiness, then produce a phased pre-submission plan.
Structured planning mode for autonomous task execution. Creates plans as MemoryDocs, executes via Missions, tracks progress with live checklist.
Require a planning-only response before implementation when a request needs design, sequencing, risk analysis, user approval, or replaces Claude-Code-style…
Gate plan mode entry with permission updates so complex tasks run in a controlled, reviewable state.
Prüft pre- and post-confirmation plan modification, changed circumstances, resolicitation and confirmation compliance im US Bankruptcy Code.
Propose new features when all trace scenarios are complete or backlog is too small. Reviews completed work and project context, then applies stv:new-task to create spec + trace…