Research and plan a new skill or agent feature

VerifiedSafe

Research and plan a new skill or agent feature before implementing. Includes checking existing skills, service state, and writing a detailed plan.

Sby Skills Guide Bot
DevelopmentIntermediate
107/25/2026
Claude Code
#research#planning#skill-creation#feature-design

Recommended for

Our review

This skill guides the research and planning of a new agent skill or feature, producing a structured plan document before any code is written.

Strengths

  • Clear two-phase structure: research first, then plan writing
  • Prevents unplanned coding by requiring explicit research
  • Produces a reusable and traceable plan document
  • Covers both technical implementation and configuration dependencies

Limitations

  • Requires the target system to have the specific infrastructure (scouts, plans directory, MCP server) described in the plan
  • Not suitable for one-line fixes or very small changes
  • Research phase may fail if live services are unavailable
When to use it

Use this skill when you need to add a new skill module, MCP tool, API endpoint, or Vue component, and you want to ensure all implications are documented before coding.

When not to use it

Do not use for minor changes (bug fixes, simple refactoring) or when the target system does not follow the MCP architecture described in the plan.

Security analysis

Safe
Quality score90/100

The skill instructs the agent to research existing skills and service state and write a plan file, without any destructive or exfiltrating actions. No code execution or dangerous commands are explicitly instructed; it's a planning aid.

No concerns found

Examples

Plan a new AWS EC2 skill
Plan a new skill for AWS EC2 instance management. The skill should list instances and allow starting/stopping them. Research existing AWS skills and the live AWS API state.
Plan a new MCP tool to ping services
Plan a new MCP tool that pings all services in the service_catalog and returns their status. Include research on current service catalog and API endpoints.
Plan a new API endpoint to expose agent logs
Plan a new API endpoint GET /api/logs that returns agent execution logs. Research existing API structure and authentication requirements.

description: Research and plan a new skill or agent feature before implementing argument-hint: <describe the skill or feature>

Phase 1 — Research (spawn scouts)

skill-scout: Check existing skills

  • Are there existing skills for this service? What patterns do they use?
  • What's in SKILL_META for similar skills (compat section especially)?
  • What does _template.py require?

service-scout: Check live service state

  • Is the target service running and reachable?
  • What version is it? What API endpoint can be probed for live_validator?
  • Does it appear in the service_catalog?

Phase 2 — Write the plan

Write to state/plans/PLAN-$ARGUMENTS.md:

# Plan: $ARGUMENTS
Date: <timestamp>
Status: pending

## Current state
<skill-scout summary>
<service-scout summary>

## What to build
Type: [ ] new skill module | [ ] new MCP tool | [ ] new API endpoint | [ ] new Vue component

### If new skill module:
File: mcp_server/tools/skills/modules/<service>_<action>.py

SKILL_META draft:
- name: <service>_<action>
- description: <one line>
- category: compute | networking | monitoring | storage | orchestration
- parameters: <dict>
- compat:
  - service: <name>
  - api_version_built_for: <version>
  - version_endpoint: <endpoint to probe>
  - version_field: <jq path to version in response>

execute() outline:
1. Read config from env/agent_settings.json
2. <core API call>
3. Return _ok/_err/_degraded

### If new MCP tool (register in server.py):
Function name: <verb_noun>
Parameters: <list>
Calls into: mcp_server/tools/<module>.py

### If API/GUI change:
Router: api/routers/<name>.py
Endpoint: <METHOD> /api/<path>
Auth required: yes/no

## Implementation steps
1. [ ] Write the module (sync, no async, _ok/_err/_degraded returns)
2. [ ] `python -m py_compile <file>` — syntax check
3. [ ] Register in server.py if MCP tool
4. [ ] Add UFW rule in hp1-infra if new port exposed
5. [ ] Test: call via API or agent commands panel
6. [ ] `/commit`

## Vault / config changes needed
<list any new env vars or vault keys neededhuman sets these>

## Out of scope
<what this plan does NOT cover>

Do NOT write any code yet. Plan only.

Related skills