plan

Generate a timestamped markdown plan in .owls/plans/ without executing commands.

1|1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/linfordWu/owls --skill plan-linfordwu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/linfordWu/owls/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/linfordWu/owls --skill plan-linfordwu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables planning-focused workflows in OWLS by generating a structured markdown plan and saving it to the active workspace, without performing any actions.

Core Features & Use Cases

  • Plan-only generation: analyze the current context and produce a concrete, ready-to-save plan rather than executing tasks.
  • Output destination: write the markdown plan to .owls/plans/ with a timestamped filename in the active workspace.
  • Real-world applicability: ideal for feature scoping, task decomposition, approval workflows, and pre-implementation reviews.

Quick Start

Describe the goal and I will generate a concrete markdown plan saved to .owls/plans/ and will not execute any actions.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a markdown plan for workspace automation without executing commands?

To generate a markdown plan without executing commands, describe your goal and a structured plan is saved to the .owls/plans/ directory with a timestamped filename. This plan includes goals, context, steps, and validation criteria without mutating the repository.

What is plan-only generation for task orchestration?

Plan-only generation for task orchestration is the process of analyzing context to produce a ready-to-save markdown plan. It outputs structured steps and validation criteria without performing any actual execution or repository mutations.

How do I structure pre-implementation reviews for local environments?

Structure pre-implementation reviews by defining goals, context, proposed steps, and validation criteria in a markdown file. This approach scopes the project upfront without applying changes to the local environment.

Does this planning workflow save files directly to the active workspace?

Yes, this planning workflow saves files directly to the active workspace. It writes the generated markdown plan to the .owls/plans/ directory using a timestamped filename for easy tracking and approval workflows.

Why use a plan-only approach for feature scoping instead of direct execution?

Use a plan-only approach for feature scoping to ensure upfront planning and approval workflows before any changes occur. It prevents repository mutations by generating actionable steps and validation criteria without executing tasks.