9.5천건 · 관련도순
Build a section-by-section paper outline from experiment results and review findings. Map claims to evidence, allocate pages for the target venue, and plan figures and citations in PAPER_PLAN.md before drafting the paper.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a vague research direction into a focused proposal and a detailed experiment roadmap. This workflow connects method refinement with validation planning, producing review records, an experiment tracker, and a summary of what to run next.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Drives a CARLA vehicle to a specific destination using navigation agents that plan routes, avoid obstacles, and obey traffic lights. Can also plan and draw a route between two points without moving the vehicle.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a pull request branch from the current branch while excluding .planning/ commits. This keeps planning documents out of the review so reviewers can focus on the code changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn existing decision records, product requirements, specifications, and other documents into GSD planning files. Create a new planning setup or add requirements and phases to an existing one, while identifying conflicts and blocking writes when contradictions remain unresolved.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn systems, code changes, plans, and data into HTML explanations built around diagrams and visual comparisons. Add interactive or animated steps where useful, with slides, PPTX exports, and MP4 videos available on request.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Open the assistant’s latest rendered message in Plannotator and return specific annotations for revision. The skill distinguishes requested edits from approval, approval with notes, and a closed session, so each review result receives the appropriate response.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create an evidence-based plan for modernizing an existing system. Analyze code and dependencies, research technology choices, and produce domain-specific migration plans with testing, rollback steps, and a consolidated roadmap for developers to execute.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Carry out a validated development plan in an isolated Git worktree, a separate working directory. Coordinate parallel implementation, run quality checks, update documentation, and take the changes through pull request creation, merging, execution metrics, and cleanup.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide a development task through requirements research, solution comparison, planning, implementation, optimization, and review. The workflow asks for approval at key stages and saves plans and completed task records in the project.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a text development plan into a visual document with diagrams, file maps, annotated code, and open questions. For interface work, add wireframes or an interactive prototype so reviewers can examine screens and behavior before implementation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Style UI for planetscale.com with extracted design tokens, named settings for colors, corner rounding, and fonts. Reuse the defined values and report missing settings when selecting the closest available alternative.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Decided cross-module refactor to phase: refactor planning - turn a decided boundary-changing refactor into a phased plan - reconnaissance, contracts-first phase order, per-phase verification and rollback, a files table, and an explicit approval gate before any edit. Use when the user says: refactor-plan, refactor plan, plan this refactor, plan the refactor, refactor planning, refactor phases, phased refactor, refactor in phases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Software feature or bugfix not yet planned: structured planning before execution. Use when the user says: plan, implementation plan, make a plan, write a plan, write the plan, task breakdown, safe feature, safely add a feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by hand and the outcomes they should expect. Use when you want to create, draft, generate, or outline a manual test plan, manual QA steps, hands-on verification steps, or an acceptance walkthrough for a feature, change, branch, plan, or PR. When the plan holds more than five tests and at least two natural categories emerge, both the test list and the detail sections are organized under plain-language categories. When nothing in the supplied context can be manually tested, it says so and asks for more context instead of producing a document. Does not analyze code for automated test coverage gaps — use automated-test-planning. Does not write test code — use tdd. Does not review code quality — use code-review. Does not stress-test an existing plan — use iterative-plan-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan. Also use it when the user asks to verify, validate, or confirm feasibility of an approach. Does not implement plan steps, write test plans, review code, or investigate bugs, and does not generate new plans from scratch — use plan-a-feature for a new plan. Runs its review rounds to completion without pausing between them; to review each round as it lands, use pairing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Take a plan all the way to a ready-to-merge pull request — review the plan (scaled to risk), implement it test-first, code-review and fix, run the CI gate, open the PR, and watch it green. Use after you have an approved plan (from plan mode, or the Plan agent); pass `issue <n>` to deliver a specific GitHub issue you name, or `next` to take the top startable issue off the project board's Ready column — either way it re-verifies, claims and plans the issue first. Invoking it with a plan already in hand is itself plan approval — it then runs autonomously to a single hard stop: ready-to-merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a marketing campaign end-to-end using Allan Dib's Before/During/After framework (The 1-Page Marketing Plan). Produces a phase-specific campaign brief with goal, audience, message, channels, assets, timeline, budget, and success metrics. Use when the user asks to plan a campaign, brief a campaign, "we need a campaign for X", launch plan, GTM plan, marketing plan for [product], demand gen plan, or any multi-channel marketing initiative. Reads ICP, services, and KPIs from knowledge/. For a full quarterly strategy rather than one campaign, see marketing-plan scope in positioning-doc and kpi-review. For the content schedule inside the campaign, see social-calendar. For the post-campaign review, see retro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure care plan templates, problems, goals, and tasks in Salesforce Health Cloud - the Integrated Care Management (ICM) model (Spring '23+, FHIR R4-aligned) and the legacy CarePlanTemplate__c + Case Tasks model. Trigger keywords: care plan template, ICM care plan, PGI library, action plan template, problem definition, goal definition. NOT for enrolling a patient into a clinical program - use admin/care-program-management. NOT for care team workflow, transition of care and SDOH barriers - use admin/care-coordination-requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. Use AFTER a plan exists. For validating the idea itself before planning, use /mk:office-hours first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
HTML-first persistent planning skill. Generates a single self-contained plan.html with interactive phases, drag-and-drop tickets, sliders, mockups, and embedded JSON state. Survives /clear via session catchup, tamper-protected by SHA-256, mirrors across 17 IDEs, ships 10 templates across Thariq's 9 categories, exports back to Markdown on demand. Use when asked to "plan it", "make me an html plan", "show me the plan", "render the plan", or when starting any multi-step task that needs a navigable artifact instead of a markdown wall.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a DRAFT 30-60-90 day onboarding plan for a new hire from the role, the team context and the systems list: phase outcomes traced to the role, activities with a named owner and due window, an access and equipment request table, learning items, manager checkpoints and the items the manager must confirm. Use when the user asks to "build an onboarding plan for our new hire", "draft the induction plan for this role", "write a first 90 days plan", "put together a new starter plan with owners", "create a ramp plan from this job description" or "plan the integration of an internal mover". Do not use for writing the job description itself, use job-description-drafter instead; for interview questions or a scorecard, use interview-scorecard-builder. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TDD Planning (Spec Anchored) - 얇은 앵커 문서(규칙 + 예제 검산표 + 미확정)를 에이전트 1회 + 사용자 리뷰 1회로 작성. --full로 3단계 풀 플로우(도메인 규칙→예시→테스트 목록). "TDD 계획 문서", "앵커 문서 작성", "테스트 목록 뽑아줘", "plan 세우고 TDD", "/tdd-plan" 요청 시 사용. 단, 요구사항 원천 문서를 먼저 만드는 것은 /tdd-plan-input, plan 합의 후 자율 구현까지는 /tdd-feature가 적합. /tdd-plan [plan-doc-path] [--full]로 호출.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for #42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR #123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming broken?", "root cause analysis on the timeout issue" COMMIT — "commit these changes", "commit the auth refactor" PR — "create a PR", "open a pull request for this branch" ISSUE — "report this to gh", "create a gh issue", "log it in github", "file a bug for this", "create a feature request" This skill triggers on ANY development task: researching, investigating, planning, building, reviewing, debugging, committing, or shipping code. NOT for: Running Archon CLI workflows in worktrees (use /archon instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.