ring:writing-plans

Translate design goals into implementation plans with file paths and verification steps.

4|Updated Jan 10, 2026

Search Tags:#planning #architecture #docs #task-breakdown #zero-context #implementation-plans

Ready to run

npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-writing-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ring:writing-plans
Source: https://github.com/LerianStudio/ring-for-opencode/tree/main/assets/skill/writing-plans
Command: npx skills add https://github.com/LerianStudio/ring-for-opencode --skill ring-writing-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates high-level design goals into concrete, executable implementation plans by generating exact file paths, complete code samples, and verification steps for engineers who may not have direct codebase context.

Core Features & Use Cases

Plan generation: produce structured docs that specify exact file paths, required components, and sample code.
Zero-context readiness: designed to deliver actionable plans even when the engineer has no prior codebase context.
Verification-driven: includes commands and success criteria to validate the plan during execution.

Quick Start

Use the ring:writing-plans skill to create an implementation plan. It should be used in a dedicated worktree orchestrated by ring:brainstorming. The agent will output a plan to docs/plans/YYYY-MM-DD-<feature>.md and prompt for execution or saving for later.

Frequently Asked Questions about ring:writing-plans

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

FAQPage Schema

How do I generate implementation plans with exact file paths and code samples?▼

Implementation plans with exact file paths and complete code samples are generated by translating high-level design goals into structured docs, specifying required components and verification steps.

What is the best way to create zero-context execution-ready docs for engineers?▼

Zero-context execution-ready docs are created by producing bite-sized tasks with explicit recovery steps, architecture notes, and verification commands, ensuring actionable plans without prior codebase context.

How do I break down architecture goals into bite-sized tasks for a design review?▼

Architecture goals are broken down into bite-sized tasks by translating high-level design goals into structured plans applicable during design reviews across backend, frontend, and infra contexts.

Can I use auto-generated plans for backend, frontend, and infra contexts?▼

Auto-generated plans can be used for backend, frontend, and infra contexts during design reviews to produce structured plans with goals, tech stack details, and verification commands.

Do I need a dedicated worktree to generate structured implementation plans?▼

A dedicated worktree orchestrated by brainstorming sessions is needed to generate structured implementation plans, which outputs to docs/plans/YYYY-MM-DD-<feature>.md and prompts for execution.

How do verification steps ensure traceability during implementation plan execution?▼

Verification steps ensure traceability by including specific commands and success criteria to validate the plan during execution, delivering structured plans with explicit recovery steps.