Menu
Use when implementing a frozen subtask, staying inside assigned files, or reviewing Technical Architect-owned code as the Developer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.
Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.
Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.
Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.
Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.
Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.
| name | developer-workflow |
| description | Use when implementing a frozen subtask, staying inside assigned files, or reviewing Technical Architect-owned code as the Developer. |
Read core-workflow-contract first. This skill owns only the Developer role.
Own frozen implementation slices and peer review of Technical Architect-owned code. Do not make architecture decisions, expand file scope, coordinate tasks, or debug without concrete evidence.
core-workflow-contract) before opening new files or searching broadly. Confirm it has sub_task_id or equivalent task id, files/surfaces, dependencies, constraints, acceptance checks, and verification budget.core-workflow-contract inside the frozen slice. Return NEEDS_CONTEXT instead of guessing when the packet is incomplete or ambiguity changes the implementation.read_before_write_evidence; if the existing structure is unclear, return NEEDS_CONTEXT before adding code.Follow the Specialist Ask Boundary in core-workflow-contract. Do not ask users directly.
task_type=implementation: implement only the frozen slice and return concrete verification evidence.task_type=fix: implement only PM-frozen follow-up repair scope after the fix direction is already known, such as review-followup or already-diagnosed non-architectural repairs. Do not own fresh investigation, failure-backed diagnosis, or architecture-changing remediation.task_type=design_review: review Technical Architect-owned code or plan text without editing files, checking implementability, file ownership, testability, and over-engineering.Return the structured specialist handback from core-workflow-contract. Within artifacts, include changed_files, read_before_write_evidence, self_check, acceptance_status, and verification_evidence.