skills.rest
ViewWay
ViewWayCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans from feature specifications with file paths and git workflows.

Updated Apr 2, 2026
Search Tags:#planning#documentation#implementation#worktree#test-driven-development#task-breakdown#git-commands
One-click install
npx skills add https://github.com/ViewWay/openclaw-skills --skill writing-plans-viewway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/ViewWay/openclaw-skills/tree/main/writing-plans
Command: npx skills add https://github.com/ViewWay/openclaw-skills --skill writing-plans-viewway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex features from specs before coding to ensure clear guidance.

Core Features & Use Cases

  • Generate end-to-end implementation plans including files to touch, tests to write, docs to consult, and commit history.
  • Produce reusable templates for feature planning across projects.
  • Use in scenarios where specs are incomplete or ambiguous to structure a plan before touching code.

Quick Start

Describe and save a complete implementation plan to docs/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan from a feature specification before coding?▼

Implementation plans from feature specifications require automating multi-step task breakdowns, precise file paths, testing plans, and reproducible git workflows into a formal markdown document to ensure clear coding guidance.

What is the best way to structure task breakdown and documentation for complex features?▼

Structuring task breakdown and documentation involves generating end-to-end implementation plans specifying exact file paths, test-driven-development steps, and commit history, saved as reusable templates for cross-project feature planning.

How do I plan a feature when the provided specifications are incomplete or ambiguous?▼

Planning features with incomplete or ambiguous specifications involves using automated plan generation to structure formal documents defining task-level steps, precise file paths, and reproducible execution instructions before touching code.

Does this implementation planning approach work with test-driven development and git workflows?▼

This implementation planning approach supports test-driven development and git workflows by automating comprehensive plans that integrate testing plans, reproducible git commands, and commit history documentation alongside task-level steps.

What format should generated implementation plan documents follow?▼

Implementation plan documents should follow a formal markdown format saved to docs/plans/YYYY-MM-DD-<feature-name>.md, containing a formal plan document header, task-level steps, precise file paths, and reproducible execution instructions.

Related Skills

Explore More Software Engineering Skills→
79yuuki79yuuki

using-git-worktrees

Create isolated Git worktrees for feature development with baseline test verification.

Community
Advanced
ianphilianphil

implement

Implement software features using strict TDD workflows from git branches and task specs.

Community
Intermediate
visualityplvisualitypl
4

create_worktree

Create a Git worktree and launch an AI implementation session for a development plan.

Official
Intermediate
jcl2018jcl2018

CJ_goal_task

Convert small ad-hoc tasks into pull requests via bash scripting.

Community
Intermediate