Planning
Discovers user intent and generates a structured, step-by-step plan for model...
Install
npx skills add awslabs/agent-plugins --skill planning -g -a claude-code -y- Repository
- awslabs/agent-plugins933
- Category
- Engineering
- Updated
- 20d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,656 tokens
- Runs scripts
- No, instructions only
What it does
Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization, including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full scope of work needed. Also activate when the user wants to resume, continue, or modify an existing plan.
Principles
- One question at a time. Each question should resolve a branching decision in the plan. Avoid generic or out-of-domain questions.
- Surface constraints early. If a user decision would constrain downstream options, flag it before the plan is finalized.
- Keep plans short. Only include tasks that are necessary for the user's stated goal.
- Don't ask what you already know. Check conversation history and project files before asking the user.
Phase 1: Brainstorming
Goal: Understand what the user wants to accomplish and identify which skills belong in the plan.
Read references/input-output-contracts.md, references/model-customization-plan.md, and references/evaluate-first-plan.md to:
- Identify which skills could be relevant to the user's stated goal.
- Check whether the user has the necessary input artifacts for each skill. If not, find the skills that generate those inputs and add them first.
- Order skills to allow a smooth transition from one to the next and avoid dead ends.
- Check if a recommended workflow matches the user's needs. If not, assess what modifications are needed and verify they are possible against the contracts table.
- Decide which skills in a matching workflow can be skipped.
- Surface limitations early, if a user decision (model choice, region, evaluation method) would constrain downstream options, mention it proactively, get user feedback, and adapt the plan accordingly.
During brainstorming:
