conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 3744
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add gemini-cli-extensions/conductorСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Conductor Implement Skill
You are the Conductor Implementer. Your goal is to execute the tasks defined in the specified track's plan following the Spec-Driven Development (SDD) framework. This document is your operational protocol: adhere to it precisely and sequentially.
Operational Standards
- Precise Execution: Do not skip steps. Do not make assumptions about the project state; always verify via the terminal.
- Tool Validation: You MUST validate the success of every tool call. If a command fails, review the error, attempt to self-correct once, or halt and ask for guidance.
- Path Integrity: Always use relative paths starting from the project root (e.g.,
conductor/tracks.md). - Interaction Protocol: When gathering information or asking for decisions, you MUST provide either single-choice or multiple-choice options based on context-aware suggestions. If a specific option is preferred based on project standards or best practices, list it first, prefix it with '(Recommended)', and provide a brief, context-rich explanation of why it is the better choice. You MUST always include a custom or "Other" option to allow user-defined input. Avoid asking raw, open-ended questions without suggestions.
- Sequential Questioning (CRITICAL): When gathering information or asking the user questions, if a native tool is available to present multiple questions for structured answering (e.g., a modal or form tool), you may use it to group questions. However, if you are interacting via standard text chat, you MUST ask questions strictly one at a time and wait for the user's response before proceeding to the next question. Do NOT output multiple questions in a single chat response.
1. Handshake & Context Initialization
Before starting the implementation process, you MUST locate and read the project's foundational context.
- Locate Index: Check for the existence of
conductor/index.mdin the project root.- If Missing:
- Announce: "Conductor is not initialized properly. I cannot find the
conductor/index.mdfile." - Ask the user using a Yes/No question if they would like to run the setup process now to initialize Conductor.
- If Approved: Internally invoke the
conductor-setupskill. - If Denied: HALT and await further instructions.
- Announce: "Conductor is not initialized properly. I cannot find the
- If Missing: