AgentSkillsCN

conductor:implement

从指定轨道的计划中执行任务。

SKILL.md
--- frontmatter
name: conductor:implement
description: Executes tasks from the specified track's plan
argument-hint: "[track name]"
disable-model-invocation: true
context: fork
agent: general-purpose
model: opus
allowed-tools: Read, Write, Edit, Bash, Glob, Grep

1.0 SYSTEM DIRECTIVE

You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to implement a track. You MUST follow this protocol precisely.

CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.

0.0 PRE-LOADED PROJECT CONTEXT

The following project files have been automatically injected at skill invocation time. If any section shows "NOT FOUND", the file does not exist — Conductor may not be set up.

Conductor Index

!cat conductor/index.md 2>/dev/null || echo "NOT FOUND — conductor/index.md does not exist."

Tracks Registry (conductor/tracks.md)

!cat conductor/tracks.md 2>/dev/null || echo "NOT FOUND — conductor/tracks.md does not exist."

Workflow (conductor/workflow.md)

!cat conductor/workflow.md 2>/dev/null || echo "NOT FOUND — conductor/workflow.md does not exist."

0.1 CONTEXT AND FILE RESOLUTION

If a user mentions a "plan" or asks about the plan, they are likely referring to the conductor/tracks.md file or one of the track plans (conductor/tracks/<track_id>/plan.md).

Universal File Resolution Protocol

PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track):

  1. •

    Identify Index: Determine the relevant index file:

    • •Project Context: conductor/index.md
    • •Track Context: a. Resolve and read the Tracks Registry (via Project Context). b. Find the entry for the specific <track_id>. c. Follow the link provided in the registry to locate the track's folder. The index file is <track_folder>/index.md. d. Fallback: If the track is not yet registered (e.g., during creation) or the link is broken: 1. Resolve the Tracks Directory (via Project Context). 2. The index file is <Tracks Directory>/<track_id>/index.md.
  2. •

    Check Index: Read the index file and look for a link with a matching or semantically similar label.

  3. •

    Resolve Path: If a link is found, resolve its path relative to the directory containing the index.md file.

    • •Example: If conductor/index.md links to ./workflow.md, the full path is conductor/workflow.md.
  4. •

    Fallback: If the index file is missing or the link is absent, use the Default Path keys below.

  5. •

    Verify: You MUST verify the resolved file actually exists on the disk.

Standard Default Paths (Project):

  • •Product Definition: conductor/product.md
  • •Tech Stack: conductor/tech-stack.md
  • •Workflow: conductor/workflow.md
  • •Product Guidelines: conductor/product-guidelines.md
  • •Tracks Registry: conductor/tracks.md
  • •Tracks Directory: conductor/tracks/

Standard Default Paths (Track):

  • •Specification: conductor/tracks/<track_id>/spec.md
  • •Implementation Plan: conductor/tracks/<track_id>/plan.md
  • •Metadata: conductor/tracks/<track_id>/metadata.json

1.1 SETUP CHECK

PROTOCOL: Verify that the Conductor environment is properly set up.

  1. •

    Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:

    • •Product Definition
    • •Tech Stack
    • •Workflow
  2. •

    Handle Failure: If ANY of these are missing (or their resolved paths do not exist), Announce: "Conductor is not set up. Please run /conductor:setup." and HALT.

2.0 TRACK SELECTION

PROTOCOL: Identify and select the track to be implemented.

  1. •

    Check for User Input: First, check if the user provided a track name as an argument (e.g., /conductor:implement <track_description>).

  2. •

    Locate and Parse Tracks Registry:

    • •The Tracks Registry content has been pre-loaded in section 0.0 PRE-LOADED PROJECT CONTEXT above. Use that content directly — do NOT re-read the file unless the pre-loaded content shows "NOT FOUND".
    • •Parse the tracks content by splitting it by the --- separator to identify each track section. For each section, extract the status ([ ], [~], [x]), the track description (from the ## heading), and the link to the track folder.
    • •CRITICAL: If no track sections are found after parsing, announce: "The tracks file is empty or malformed. No tracks to implement." and halt.
  3. •

    Continue: Immediately proceed to the next step to select a track.

  4. •

    Select Track:

    • •If a track name was provided:
      1. •Perform an exact, case-insensitive match for the provided name against the track descriptions you parsed.
      2. •If a unique match is found, confirm the selection with the user: "I found track '<track_description>'. Is this correct?"
      3. •If no match is found, or if the match is ambiguous, inform the user and ask for clarification. Suggest the next available track as below.
    • •If no track name was provided (or if the previous step failed):
      1. •Identify Next Track: Find the first track in the parsed tracks file that is NOT marked as [x] Completed.
      2. •If a next track is found:
        • •Announce: "No track name provided. Automatically selecting the next incomplete track: '<track_description>'."
        • •Proceed with this track.
      3. •If no incomplete tracks are found:
        • •Announce: "No incomplete tracks found in the tracks file. All tasks are completed!"
        • •Halt the process and await further user instructions.
  5. •

    Handle No Selection: If no track is selected, inform the user and await further instructions.

3.0 TRACK IMPLEMENTATION

PROTOCOL: Execute the selected track.

  1. •

    Announce Action: Announce which track you are beginning to implement.

  2. •

    Update Status to 'In Progress':

    • •Before beginning any work, you MUST update the status of the selected track in the Tracks Registry file.
    • •This requires finding the specific heading for the track (e.g., ## [ ] Track: <Description>) and replacing it with the updated status (e.g., ## [~] Track: <Description>) in the Tracks Registry file you identified earlier.
  3. •

    Load Track Context: a. Identify Track Folder: From the tracks file, identify the track's folder link to get the <track_id>. b. Read Files: - Track Context: Using the Universal File Resolution Protocol, resolve and read the Specification and Implementation Plan for the selected track. - Workflow: The Workflow has been pre-loaded in section 0.0 PRE-LOADED PROJECT CONTEXT above. Use that content directly — do NOT re-read unless the pre-loaded content shows "NOT FOUND". c. Error Handling: If you fail to read any of these files, you MUST stop and inform the user of the error.

  4. •

    Execute Tasks and Update Track Plan: a. Announce: State that you will now execute the tasks from the track's Implementation Plan by following the procedures in the Workflow. b. Iterate Through Tasks: You MUST now loop through each task in the track's Implementation Plan one by one. c. For Each Task, You MUST: i. Defer to Workflow: The Workflow file is the single source of truth for the entire task lifecycle. You MUST now read and execute the procedures defined in the "Task Workflow" section of the Workflow file you have in your context. Follow its steps for implementation, testing, and committing precisely.

  5. •

    Finalize Track:

    • •After all tasks in the track's local Implementation Plan are completed, you MUST update the track's status in the Tracks Registry.
    • •This requires finding the specific heading for the track (e.g., ## [~] Track: <Description>) and replacing it with the completed status (e.g., ## [x] Track: <Description>).
    • •Commit Changes: Stage the Tracks Registry file and commit with the message chore(conductor): Mark track '<track_description>' as complete.
    • •Announce that the track is fully complete and the tracks file has been updated.

4.0 SYNCHRONIZE PROJECT DOCUMENTATION

PROTOCOL: Update project-level documentation based on the completed track.

  1. •

    Execution Trigger: This protocol MUST only be executed when a track has reached a [x] status in the tracks file. DO NOT execute this protocol for any other track status changes.

  2. •

    Announce Synchronization: Announce that you are now synchronizing the project-level documentation with the completed track's specifications.

  3. •

    Load Track Specification: Read the track's Specification.

  4. •

    Load Project Documents:

    • •Resolve and read:
      • •Product Definition
      • •Tech Stack
      • •Product Guidelines
  5. •

    Analyze and Update: a. Analyze Specification: Carefully analyze the Specification to identify any new features, changes in functionality, or updates to the technology stack. b. Update Product Definition: i. Condition for Update: Based on your analysis, you MUST determine if the completed feature or bug fix significantly impacts the description of the product itself. ii. Propose and Confirm Changes: If an update is needed, generate the proposed changes. Then, present them to the user for confirmation: > "Based on the completed track, I propose the following updates to the Product Definition:" > diff > [Proposed changes here, ideally in a diff format] > > "Do you approve these changes? (yes/no)" iii. Action: Only after receiving explicit user confirmation, perform the file edits to update the Product Definition file. Keep a record of whether this file was changed. c. Update Tech Stack: i. Condition for Update: Similarly, you MUST determine if significant changes in the technology stack are detected as a result of the completed track. ii. Propose and Confirm Changes: If an update is needed, generate the proposed changes. Then, present them to the user for confirmation: > "Based on the completed track, I propose the following updates to the Tech Stack:" > diff > [Proposed changes here, ideally in a diff format] > > "Do you approve these changes? (yes/no)" iii. Action: Only after receiving explicit user confirmation, perform the file edits to update the Tech Stack file. Keep a record of whether this file was changed. d. Update Product Guidelines (Strictly Controlled): i. CRITICAL WARNING: This file defines the core identity and communication style of the product. It should be modified with extreme caution and ONLY in cases of significant strategic shifts, such as a product rebrand or a fundamental change in user engagement philosophy. Routine feature updates or bug fixes should NOT trigger changes to this file. ii. Condition for Update: You may ONLY propose an update to this file if the track's Specification explicitly describes a change that directly impacts branding, voice, tone, or other core product guidelines. iii. Propose and Confirm Changes: If the conditions are met, you MUST generate the proposed changes and present them to the user with a clear warning: > "WARNING: The completed track suggests a change to the core Product Guidelines. This is an unusual step. Please review carefully:" > diff > [Proposed changes here, ideally in a diff format] > > "Do you approve these critical changes to the Product Guidelines? (yes/no)" iv. Action: Only after receiving explicit user confirmation, perform the file edits. Keep a record of whether this file was changed.

  6. •

    Final Report: Announce the completion of the synchronization process and provide a summary of the actions taken.

    • •Construct the Message: Based on the records of which files were changed, construct a summary message.
    • •Commit Changes:
      • •If any files were changed (Product Definition, Tech Stack, or Product Guidelines), you MUST stage them and commit them.
      • •Commit Message: docs(conductor): Synchronize docs for track '<track_description>'
    • •Example (if Product Definition was changed, but others were not):

      "Documentation synchronization is complete.

      • •Changes made to Product Definition: The user-facing description of the product was updated to include the new feature.
      • •No changes needed for Tech Stack: The technology stack was not affected.
      • •No changes needed for Product Guidelines: Core product guidelines remain unchanged."
    • •Example (if no files were changed):

      "Documentation synchronization is complete. No updates were necessary for project documents based on the completed track."

5.0 TRACK CLEANUP

PROTOCOL: Offer to archive or delete the completed track.

  1. •

    Execution Trigger: This protocol MUST only be executed after the current track has been successfully implemented and the SYNCHRONIZE PROJECT DOCUMENTATION step is complete.

  2. •

    Ask for User Choice: You MUST prompt the user with the available options for the completed track.

    "Track '<track_description>' is now complete. What would you like to do? A. Review (Recommended): Run the review command to verify changes before finalizing. B. Archive: Move the track's folder to conductor/archive/ and remove it from the tracks file. C. Delete: Permanently delete the track's folder and remove it from the tracks file. D. Skip: Do nothing and leave it in the tracks file. Please enter the option of your choice (A, B, C, or D)."

  3. •

    Handle User Response:

    • •If user chooses "A" (Review):
      • •Announce: "Please run /conductor:review to verify your changes. You will be able to archive or delete the track after the review."
    • •If user chooses "B" (Archive): i. Create Archive Directory: Check for the existence of conductor/archive/. If it does not exist, create it. ii. Archive Track Folder: Move the track's folder from its current location (resolved via the Tracks Directory) to conductor/archive/<track_id>. iii. Remove from Tracks File: Read the content of the Tracks Registry file, remove the entire section for the completed track (the part that starts with --- and contains the track description), and write the modified content back to the file. iv. Commit Changes: Stage the Tracks Registry file and conductor/archive/. Commit with the message chore(conductor): Archive track '<track_description>'. v. Announce Success: Announce: "Track '<track_description>' has been successfully archived."
    • •If user chooses "C" (Delete): i. CRITICAL WARNING: Before proceeding, you MUST ask for a final confirmation due to the irreversible nature of the action. > "WARNING: This will permanently delete the track folder and all its contents. This action cannot be undone. Are you sure you want to proceed? (yes/no)" ii. Handle Confirmation: - If 'yes': a. Delete Track Folder: Resolve the Tracks Directory and permanently delete the track's folder from <Tracks Directory>/<track_id>. b. Remove from Tracks File: Read the content of the Tracks Registry file, remove the entire section for the completed track, and write the modified content back to the file. c. Commit Changes: Stage the Tracks Registry file and the deletion of the track directory. Commit with the message chore(conductor): Delete track '<track_description>'. d. Announce Success: Announce: "Track '<track_description>' has been permanently deleted." - If 'no' (or anything else): a. Announce Cancellation: Announce: "Deletion cancelled. The track has not been changed."
    • •If user chooses "D" (Skip) or provides any other input:
      • •Announce: "Okay, the completed track will remain in your tracks file for now."