القائمة
Publish a one-session implementation plan for /implement-plan — escape hatch when the build fits one context window.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way is clear. On ticket close, may offer ADRs (promotion into docs/adr/) when ADR-POLICY criteria hold.
Sharpen a plan or design against this codebase via grilling + domain-modeling (CONTEXT.md / ADR offers). May offer /wayfinder when fog appears. Invoke with `/grill-with-docs`.
Applies Dockerfile, Docker Compose, BuildKit, and container security patterns for local development and hardened deployable images. Use when authoring Dockerfiles or compose files, wiring secrets (runtime vs build-time), reproducible bases, PID 1 and healthchecks, volumes and networking, supply-chain hygiene, or troubleshooting compose stacks.
Routes Go work to the right reference guides and conventions for the task. Use when working on Go architecture, implementation, refactoring, concurrency, error handling, testing, performance, or code review.
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Use when writing SQL or migrations, designing schemas, troubleshooting slow queries, implementing Row Level Security, tuning connection pooling, or reviewing database changes. Based on Supabase-leaning Postgres practice.
Applies Python idioms, PEP 8 norms, typing, packaging, concurrency, tooling, and performance discipline to everyday Python code. Use when writing, reviewing, refactoring, or packaging Python; when the user names type hints, dataclasses, pytest, ruff/black/mypy, asyncio, concurrency, EAFP vs LBYL, or Python idioms; or asks for a Python-specific code-quality pass.
استنادا إلى تصنيف SOC المهني
| name | to-plan |
| description | Publish a one-session implementation plan for /implement-plan — escape hatch when the build fits one context window. |
| disable-model-invocation | true |
Synthesize an implementation plan from what you already know — do not interview. Default artifact: work/<feature-slug>/plan.md. If docs/agents/issue-tracker.md exists, follow it; otherwise assume local work/. Run /setup-work only for a non-default tracker.
SSOT is the markdown plan. HTML is an optional review render only — /implement-plan reads the .md.
When you need a discrete decision with a small set of clear options (about 2–6), prefer the AskQuestion tool so the user gets structured choices. Ask one decision at a time when this skill already sequences questions that way.
If AskQuestion is unavailable in the current environment, ask the same choices in ordinary chat (same options, same ordering).
Use plain chat for free-form answers.
Gather context (conversation, named map/spec links). Prefer glossary vocabulary; respect ADRs. Done when: constraints for the build are listed or linked.
Size check (recommend, user confirms): would clearing context halfway force re-deriving seams, contracts, or open edge cases?
/to-spec → /to-tickets → /implement./to-spec first, then choose tickets vs plan.Sketch seams briefly (prefer existing, highest; fewer is better). Confirm if non-obvious. Done when: seams are agreed or accepted.
Write and publish the plan (work/<feature-slug>/plan.md locally, or tracker equivalent).
Done when: plan.md (or tracker equivalent) exists with the template sections filled.
HTML (optional): If the user already said “with HTML,” write plan.html beside the plan per references/PLAN-HTML.md. Otherwise AskQuestion — write HTML review companion? — default No.
Done when: HTML written if requested/accepted, or skipped.
Hard stop. Tell the user to run /implement-plan against the plan file. Do not start /implement-plan unless asked in the same turn.
Done when: user knows the plan path; heavy stack not started unless asked.
What the user gets when this plan is done — one or two sentences.
Where behavior will be tested. Prefer existing seams; note any new ones.
Numbered, ordered, verifiable steps sized for one fresh agent session — if you cannot keep them that small, abort and recommend /to-spec instead.
What this plan will not do.
Acceptance checks for the overall plan (not layer-by-layer file lists).
Avoid specific file paths or large code dumps — they go stale. Exception: trim prototype snippets that encode a decision (state machine, schema, type shape) and note they came from a prototype.