9.5천건 · 관련도순
Manage projects involving multiple Workers with a shared plan that records task status, assignments, and dependencies. It covers project setup, task completion updates, plan changes, blocked work, and final notifications to the administrator.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create an interactive HTML implementation plan that connects proposed behavior to mockups, code, and data structures. Readers can explore details, choose options, edit schemas, and return comments before development starts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Apply improvement plans from skill-quality-reviewer to Claude Skills. Groups edits by file, handles conflicting recommendations by priority, backs up originals, and verifies the updates before producing a report of changes and verification results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize complex tasks using persistent Markdown files for plans, research notes, and final deliverables. Track completed phases, decisions, and errors, and revisit the plan before major actions to keep work aligned with its goal.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run a research task through five ordered stages: brainstorming, planning, implementation, review, and documentation. The workflow checks that brainstorming and planning files exist before proceeding, then reviews and documents what the implementation stage produced.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a research task or estimation problem into a saved implementation plan grounded in project code, prior decisions, and relevant methods. Adjust the detail to the task and document dependencies, risks, diagnostics, and acceptance criteria.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare competing plans from AI agents against the actual task and available evidence. Choose one, combine useful parts, or request revisions, then produce a single execution handoff with ordered steps, verification checks, and reasons for rejected alternatives.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a multi-step feature into an implementation plan that another engineer can follow without prior context. The plan includes exact file paths, complete code, test commands, expected results, and small, verifiable steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn feature requests and conversation context into an implementation plan and handoff document. Review existing code, clarify complex requirements, and organize concrete tasks, affected files, verification steps, assumptions, and risks for review before implementation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Carry out technical plans in verified stages, with automated checks followed by human review. The skill defines task delegation, progress tracking, and persistent handoff records so work can resume with the context needed for the next task.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn implementation plans and specifications into an ordered tasks.md checklist. Organize work around user stories, meaning goals expressed from a user's perspective, with file paths, dependencies, parallel work opportunities, and independent verification criteria.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize complex tasks using three Markdown files for plans, findings, and progress. The skill keeps decisions, discoveries, errors, and test results in project files that an agent can consult when making decisions or resuming work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify implementation choices before planning through focused questions, existing project context, and codebase exploration. Record decisions in a context file that guides subsequent research and planning, with options for automatic defaults or answering questions in a file.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
SUPERSEDED by /claudex-loop (formerly /crucible; adds a Phase 0 research/recon pass + rebuilt interview) — prefer that skill unless you explicitly want this one. Two-act plan hardening. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan or design, one question at a time, recommending an answer for each and exploring the codebase when it can answer itself, until every branch of the decision tree is resolved. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-me-codex", "grill me then have codex review", "grill me and stress-test the plan", "interview me about this plan then get a second model on it", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants both alignment AND a cross-model sanity check before implementation. Builds on Matt Pocock's grill-me (MIT). For the docs-aware variant use /grill-with-docs-codex; if you already have a plan and want only the Codex review use /codex-review. NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create financial plans for Chinese wealth management clients covering retirement, education, estate, and cash-flow planning. Adapted from the original financial-plan skill for Chinese tax rules, social security, and local financial products. Triggers on "A股财务规划", "理财规划", "financial plan China", "retirement plan China", "财务规划客户", "退休规划", "教育金规划", or "comprehensive financial plan".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test code — use tdd to implement behavior test-first. Does not refine existing plans — use iterative-plan-review. Does not review code quality, security, or style — use code-review for full code review. Does not evaluate architectural testability or structural coupling — use architectural-analysis for architectural assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not plan to local files only — use plan-a-feature. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features to Confluence — use project-documentation-to-confluence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write code through a disciplined, BDD-framed Test-Driven Development loop: build a behavior test list, then drive each behavior through red-green-refactor with an enforced observed-failure gate. Use when the user wants to implement, build, or write code test-first, "do TDD", follow "red-green-refactor", drive code from tests, choose the next test by the Transformation Priority Premise (TPP) or ZOMBIES ordering, or grow a feature behavior-by-behavior with tests leading. This skill writes and changes code; it does not produce a test plan document (use automated-test-planning, or manual-test-planning for a plan a person runs by hand), review or audit existing code (use code-review), restructure existing code outside a TDD loop (use refactor, or plan-a-change to plan a multi-module restructure), specify what a feature should do (use plan-a-feature), or find the root cause of a bug (use investigate). Runs its loop to completion without pausing for review; to review each behavior as it lands, use pairing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarially review the current implementation plan with three independent critic subagents, reconcile their findings into a consensus, and apply the agreed feedback to the plan. Use after drafting a plan (in plan mode or a plan/design doc) and before starting implementation, or whenever the user asks to pressure-test, critique, or harden a plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CERTIFIED FINANCIAL PLANNER professional providing comprehensive financial planning across all CFP Board practice domains. Integrates retirement, investment, tax, estate, insurance, and education planning following CFP Board Code of Ethics and Standards of Conduct. Use for holistic financial plans, cash flow analysis, net worth statements, insurance needs, estate planning coordination, education funding (529 plans), tax strategies, retirement projections, or CFP Board Practice Standards compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Your Personal Finance Manager for Canadians — an AI financial planning partner that conducts thorough financial interviews, builds complete plans, generates interactive dashboards, and provides ongoing coaching. Use this skill whenever someone asks about budgeting, saving, investing, debt strategy, retirement planning, tax optimization, government benefits, insurance, RRSPs, TFSAs, RESPs, CPP, OAS, or any aspect of personal finance in a Canadian context. Also triggers for "should I buy this?", "can I afford this?", financial check-ins, plan updates, life change impacts on finances, or any request to build or review a financial plan. Even if the user just says "help me with my money" or "I need a budget", this skill should activate. Canada-focused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.