Agent skill

plan

Enter planning mode to research and analyze before implementation. Use when user wants to plan a feature, evaluate a technical approach, explore architectural decisions, or think through implementation before coding. Triggers on "plan", "think through", "analyze", "evaluate approach", "design decision", "before we implement", "let's research", or when proposing significant changes.

View SKILL.md on GitHub Repository
Stars 27
Forks 4

Install this agent skill to your Project

npx add-skill https://github.com/frmlabz/frm-stack/tree/main/capabilities/general/skills/plan

SKILL.md

Planning Mode

Enter planning mode to research, analyze, and document a considered approach before implementation. Output a plan document to .work/plans/backlog/<name>.md.

Planning Workflow

1. Understand the Request

Clarify what needs planning:

  • What problem are we solving?
  • What constraints exist (time, tech stack, team familiarity)?
  • Is there prior art in this codebase?

Ask clarifying questions before researching.

2. Research the Codebase

Investigate relevant areas:

  • Existing patterns and conventions
  • Related implementations
  • Database schema and data models
  • API contracts and boundaries
  • Configuration and environment requirements

Use codebase_search, grep, and read_file to gather context.

3. Research Technologies

When introducing or evaluating technologies:

  • Fetch current documentation using available tools
  • Check compatibility with existing stack (Node.js, TypeScript, pnpm, etc.)
  • Evaluate maturity, maintenance status, bundle size implications

4. Analyze Trade-offs

For each approach considered:

  • Benefits: What problems does it solve well?
  • Drawbacks: What complexity or limitations does it introduce?
  • Risks: What could go wrong? Migration paths?
  • Alternatives: What else was considered and why not?

5. Write the Plan

Create .work/plans/backlog/<descriptive-name>.md with:

markdown
# Plan: <Title>

**Status:** Draft | Review | Approved
**Created:** <date>
**Author:** <who requested>

## Context

What triggered this plan? Link to conversations, issues, or user requests.

## Problem Statement

One paragraph: what problem are we solving and why it matters.

## Research Findings

### Codebase Analysis
- Relevant existing patterns
- Files/modules that will be affected
- Current state vs desired state

### Technology Evaluation
- Options considered
- Compatibility notes
- Documentation links

## Proposed Approach

Clear description of the recommended solution.

### Why This Approach
- Key benefits
- How it fits existing patterns

### Trade-offs Accepted
- Known limitations
- Complexity being introduced

### Alternatives Considered

| Approach | Pros | Cons | Why Not |
|----------|------|------|---------|
| ... | ... | ... | ... |

## Open Questions

- Unresolved decisions needing input
- Areas requiring more research
- Questions for the team

## Next Steps

- [ ] Specific actionable items
- [ ] Who needs to review/approve
- [ ] Dependencies or blockers

Output Guidelines

  • Be concise: Developers will read this. Respect their time.
  • Be specific: Link to actual files, functions, line numbers.
  • Be honest: Surface unknowns and risks clearly.
  • Be decisive: Recommend an approach, don't just list options.

When Planning Completes

After writing the plan:

  1. Summarize the recommendation to the user
  2. Highlight key trade-offs and open questions
  3. Ask if they want to proceed, modify, or research further
  4. If approved, the plan can be used to generate tasks via the task skill

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

frmlabz/frm-stack

testing

Shared database testing patterns with testcontainers and Vitest. Use when writing backend tests, setting up test files, debugging test failures, or configuring Vitest. Triggers on "write tests", "test setup", "testcontainers", "vitest config", "test isolation", or when creating new test suites.

27 4
Explore
frmlabz/frm-stack

db-workflow

Database workflow with Postgres, Kysely, and Atlas migrations. Use when modifying database schema, creating migrations, generating TypeScript types, or troubleshooting database issues. Triggers on "schema change", "migration", "db-migrate", "kysely", "atlas", or when editing db/schema.sql.

27 4
Explore
frmlabz/frm-stack

mobile-auth

Better Auth integration with Expo/React Native. Use when working on mobile authentication, session management, or debugging auth issues in the mobile app. Triggers on "mobile auth", "expo auth", "better-auth expo", "session provider", "SecureStore", or when editing apps/frontend/mobile auth files.

27 4
Explore
frmlabz/frm-stack

react-useeffect

React useEffect best practices from official docs. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization. Teaches when NOT to use Effect and better alternatives.

27 4
Explore
frmlabz/frm-stack

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

27 4
Explore
frmlabz/frm-stack

resolve-pr-comments

Address GitHub PR review comments end-to-end, fetch unresolved review threads (via `gh` GraphQL), implement fixes, reply with what changed, and resolve threads using the bundled scripts. Use when asked to “address PR comments”, “resolve review threads”, or “clear requested changes”.

27 4
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results