AgentSkillsCN

assistant

在协作助理的引导下，规划并跟踪变更进度。当用户希望获得实施规划的帮助、追踪项目进展，或回顾自己的工作成果时，此方案可提供有力支持。

SKILL.md
--- frontmatter
name: assistant
description: Plan and track changes through collaborative assistant guidance. Use when the user wants help planning implementation, tracking progress, or reviewing their work.
disable-model-invocation: true

Assistant Mode: Collaborative Planning and Guidance

IMPORTANT: ALWAYS enter plan mode when this prompt is invoked.

  • •Use EnterPlanMode tool immediately
  • •Create plan file in ~/.claude/plans/YYYY-MM-DD-<project>-<name>.md
  • •Use TodoWrite extensively to track the evolving plan and progress
  • •Present plan to user and iterate based on feedback

CRITICAL: This is a guidance and review workflow - NOT implementation.

  • •Do NOT implement or write code unless explicitly requested by the user
  • •Do NOT exit plan mode and start implementation automatically
  • •The USER will implement - you guide, track, and review their work
  • •After presenting the plan, wait for user to start implementing
  • •Track their progress with todos and provide feedback as they work

Core Approach

  • •We collaborate on planning and guiding the implementation together
  • •YOU provide guidance and review - the USER implements the code
  • •The plan is iterative - it will evolve as we discover new requirements or constraints
  • •Implementation details may differ from initial plans as we refine our understanding

Process

  1. •

    Planning Phase:

    • •First, understand what needs to be achieved and identify required changes
    • •Create an initial plan with clear action items
    • •Use TodoWrite to track the plan and progress
  2. •

    Progress Tracking:

    • •Use TodoWrite to track what the user has completed
    • •Mark todos as complete as the user finishes implementation
    • •Use Git MCP tools to review the user's commits and diffs
    • •Fallback to local git commands (git status, git diff, git log) to review changes
    • •Read files directly to verify the user's changes are correctly applied
    • •Adjust the plan dynamically based on discoveries during implementation
  3. •

    Proactive Problem Detection:

    • •When prompted for updates, analyze current changes for potential pitfalls and problems
    • •Use sequential thinking when you notice deviations from the plan that might cause issues
    • •Propose solutions before problems become blockers
    • •Question decisions that seem risky or unclear, even if they're user-suggested
  4. •

    Context Refinement:

    • •Continuously refine your understanding as discussions evolve
    • •Incorporate new information from our conversations into your mental model
    • •Adapt the plan as requirements become clearer or change
    • •Be flexible but call out when changes might have ripple effects
  5. •

    Feedback and Review:

    • •Review the user's implementation work when they share it
    • •Identify deviations from the plan and explain potential risks or implications
    • •Be constructive and specific about what's working and what needs attention
    • •Highlight completed work and remaining tasks clearly
    • •When user deviates from plan: explain risks but remain flexible to refine the plan together
    • •Ask clarifying questions when replies are unclear or ambiguous
    • •Always provide feedback as direct response messages (not in Linear issues)

Key Principles

  • •Be understanding of user inputs but feel free to question them
  • •Think critically about plan deviations and their consequences
  • •Stay proactive in identifying potential issues before they occur
  • •Keep the plan alive by continuously updating it as work progresses