designing-before-coding

Create structured implementation plans before coding new features.

11|Updated Sep 6, 2011

Search Tags:#design #planning #feature development #implementation #software architecture

Ready to run

npx skills add https://github.com/tclem/dotfiles --skill designing-before-coding-tclem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: designing-before-coding
Source: https://github.com/tclem/dotfiles/tree/main/copilot/skills/designing-before-coding
Command: npx skills add https://github.com/tclem/dotfiles --skill designing-before-coding-tclem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams and developers organize their approach by emphasizing the importance of upfront design, reducing costly rework later.

Core Features & Use Cases

Planning Before Coding: Guides users through understanding requirements and exploring multiple solutions before making changes.
Design Documentation: Assists in creating clear plans that detail file involvement, data flow, validation, and success criteria.
Use Case: When adding a new feature, use this Skill to draft a design plan outlining involved files and potential pitfalls, ensuring smooth implementation.

Quick Start

Describe the design approach for integrating a new authentication method before making code changes.

Frequently Asked Questions about designing-before-coding

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

FAQPage Schema

Why plan software architecture before coding a new feature?▼

Planning software architecture before coding ensures comprehensive understanding of requirements and comparison of design approaches, reducing costly rework and aligning implementation with project goals.

How do I create a design document for feature development?▼

To create a design document for feature development, outline involved files, data flow, validation rules, and success criteria to ensure smooth implementation and well-prepared code changes.

What's the best way to explore multiple solutions before implementing modifications?▼

The best way to explore solutions before implementing modifications is using structured planning to compare approaches, understand requirements thoroughly, and create a detailed implementation plan.

Does this approach work for designing a new authentication method integration?▼

Yes, this approach works for designing a new authentication method by guiding you to draft a design plan outlining involved files, data flow, and potential pitfalls before making code changes.

What should be included in an implementation plan for software architecture decisions?▼

An implementation plan for software architecture decisions should include file involvement, data flow, validation rules, success criteria, and potential pitfalls to ensure well-prepared and aligned code changes.