Research and plan

Skill fredrick84823/fstack/skills/research-and-plan

Research the codebase and create a concise implementation plan in one step. Use for small, focused changes where you want to go straight from research to a ready-to-implement plan without back-and-forth. For larger or more complex changes, use /research-codebase followed by /create-plan instead.From its SKILL.md

Install

npx -y skills add fredrick84823/fstack --skill research-and-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

Research and Plan

Research the codebase, then write a concise plan. No interactive Q&A — just research and output.

Exploration Tools Priority

For code file exploration, prefer smart-explore tools (4-18x token savings):

Tool	Use instead of
`smart_search(query, path)` — discover files + symbols in one call	Glob + Grep discovery loop
`smart_outline(file_path)` — structural skeleton (~1-2k tokens)	Read on files > 100 lines
`smart_unfold(file_path, symbol_name)` — one symbol's full source	Read on large files for one function

Rule: Use Read only for files < 100 lines or non-code files (markdown, JSON, config).

Process

1. Read Mentioned Files First

For code files > 100 lines, prefer smart_outline + smart_unfold over Read. For small files, config, or markdown: use Read directly.

2. Research in Parallel

Spawn:

codebase-locator: Find WHERE relevant files/components live
codebase-analyzer: Understand HOW the affected code currently works

If thoughts/ exists, also spawn:

thoughts-locator: Find relevant prior context

Wait for ALL to complete.

3. Write Concise Plan

If thoughts/ exists: thoughts/shared/plans/YYYY-MM-DD-description.md Otherwise: choose a sensible path in the project

# Plan: [Task]

## What & Why
[1-2 sentences]

## Current State
- `path/to/file:line` — [what exists now]

## Changes

### 1. [Component/File]
**File**: `path/to/file`
- [Specific change, with line reference if applicable]

### 2. [Next component]
...

## Success Criteria
- [ ] [Automated check]
- [ ] [Manual verification]

## Out of Scope
- [What we're NOT doing]

4. Present

Show plan location and a one-line summary. Ask: "Does this look right, or anything to adjust?"