skills.rest
chianyungcode
chianyungcodeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

think-steps

Convert feature ideas into non-technical flows and technical implementation plans.

Updated Feb 14, 2025
Search Tags:#planning#checkpoints#pseudocode#feature-flow#implementation-plan#manual-guidance#think-steps
One-click install
npx skills add https://github.com/chianyungcode/dotfiles --skill think-steps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: think-steps
Source: https://github.com/chianyungcode/dotfiles/tree/main/chezmoi/dot_config/opencode-thinking/skills/think-steps
Command: npx skills add https://github.com/chianyungcode/dotfiles --skill think-steps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users convert a feature idea, bug, or behavior into a clear non-technical flow and a practical technical plan, enabling thinking before coding.

Core Features & Use Cases

  • Separate the user-facing flow from the technical steps to keep thinking and implementation scoped.
  • Provide implementation checkpoints and optional pseudocode instead of full-code scaffolds.
  • Tailor the plan to the project's patterns and common workflows, such as authentication, routing, data handling, and UI behavior.

Quick Start

Describe your feature request in plain language, and I will generate a non-technical flow followed by a concrete technical plan.

Frequently Asked Questions about think-steps

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

FAQPage Schema
How do I turn a feature idea into an implementation plan before coding?▼

Converting a feature idea into an implementation plan requires separating the user-facing flow from technical steps. You describe the feature in plain language to generate a non-technical flow followed by a concrete technical plan with checkpoints.

What is the best way to break down UI behavior and routing into coding steps?▼

Breaking down UI behavior and routing into coding steps involves creating a non-technical flow alongside a technical plan tailored to project patterns. This approach provides implementation checkpoints and optional pseudocode instead of full-code scaffolds.

Can I get pseudocode and checkpoints instead of full code scaffolds for a new feature?▼

Yes, you can get pseudocode and implementation checkpoints instead of full code scaffolds. Describing your feature request in plain language generates a practical technical plan that keeps thinking and implementation scoped without writing the actual code.

How do I plan authentication and data handling flows for manual coding?▼

Planning authentication and data handling flows involves mapping out a non-technical user flow and aligning a technical plan with existing project patterns. This ensures your manual coding guidance covers step-by-step behavior for these common workflows.

Does this approach work for planning bug fixes and behavior breakdowns?▼

Yes, this approach works for planning bug fixes and behavior breakdowns. Converting a bug or behavior into a clear flow and technical plan enables structured thinking before coding, helping you scope the fix and implementation accurately.

Related Skills

Explore More Software Engineering Skills→
knishiokaknishioka
7

daily-report-generator

Generate daily and weekly reports from Git commit logs and calendar data.

Community
Intermediate
JubaKitiashviliJubaKitiashvili
41

continuous-learning-v2

Extract recurring coding patterns from development sessions into reusable rules and skills.

Community
Advanced
feasibleonefeasibleone
1

blong-adapter

Integrate Blong with external systems via HTTP, TCP, and SQL adapters.

Official
Advanced
KraitsKraits

writing-plans

Convert a written spec into a step-by-step implementation plan.

Community
Intermediate