plan-feature

Plan lightweight implementation strategies for medium-scope features with plan artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-feature-dthompson-jti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/dthompson-jti/safety-check-app-concept/tree/main/.agent/skills/plan/feature
Command: npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-feature-dthompson-jti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create a lightweight, shareable implementation plan for medium-scope features (typically 1-5 files), reducing the need for a full PRD while guiding execution.

Core Features & Use Cases

  • Artifacts: outlines required plan artifacts such as implementation_plan.md and task.md to document scope and boundaries.
  • Structured approach: provides phased discovery, strategy evaluation, and phased execution to decompose features into actionable steps.
  • Use Case: for a feature like "advanced search" or "multi-step onboarding," produce a compact plan with milestones and ownership.

Quick Start

Draft a lightweight implementation plan for a medium-scope feature.

Frequently Asked Questions about plan-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan for a medium-scope feature without a full PRD?

Yes, a lightweight implementation plan replaces a full PRD for medium-scope features by providing a structured planning workflow with discovery, strategy evaluation, phased execution, and reflective review, outputting implementation_plan.md and task.md artifacts.

What is phased execution in feature planning?

Phased execution in feature planning decomposes medium-scope features into actionable milestones, providing a clear artifact trail through implementation_plan.md and task.md before development begins.

Does this structured planning workflow work for features spanning 1-5 files?

This structured planning workflow is designed specifically for medium-scope features spanning 1-5 files, providing a lightweight, shareable implementation plan with milestones and ownership to guide execution.

What's the best way to document scope and boundaries for a multi-step onboarding feature?

The best way to document scope and boundaries for a multi-step onboarding feature is generating compact plan artifacts like implementation_plan.md and task.md, which define constraints and outline a phased execution strategy.

When should I not use a lightweight implementation plan?

You should not use a lightweight implementation plan for features outside the 1-5 file range or those lacking requirements for a structured planning workflow with discovery, strategy options, phased execution, and reflective review.