design-feature

Generate structured design documents with task breakdowns for new software features.

160|16|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/janekbaraniewski/openusage --skill design-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-feature
Source: https://github.com/janekbaraniewski/openusage/tree/main/.opencode/skills/design-feature
Command: npx skills add https://github.com/janekbaraniewski/openusage --skill design-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps in the process of designing a new feature by providing a structured approach to exploration, documentation, and task breakdown.

Core Features & Use Cases

  • Feature Quizzing: Asks targeted questions to clarify feature requirements and scope.
  • Codebase Exploration: Can analyze and provide insights into relevant parts of the codebase.
  • Design Document Generation: Assists in writing a design document, including breaking down the feature into actionable tasks.
  • Use Case: A product manager wants to design a new notification system. This skill can help them define the requirements, understand existing notification logic in the codebase, and generate a design document with implementation tasks.

Quick Start

Use the design-feature skill to design a new user profile editing feature.

Frequently Asked Questions about design-feature

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

FAQPage Schema
How do I design a new software feature and generate a design document?

Design a new software feature by using interactive quizzing to clarify requirements, exploring your codebase for context, and generating a structured design document with actionable task breakdowns.

What is the best way to break down feature requirements into actionable tasks?

Break down feature requirements by defining the feature specifications through targeted quizzing, then translating those clarified requirements into a structured implementation plan of actionable tasks.

Can I explore my codebase to understand existing logic before designing a feature?

Yes, you can explore your codebase to analyze and gain insights into relevant existing logic, which provides necessary context for defining accurate feature specifications and implementation plans.

Does this feature design process work for product managers and engineers?

Feature design works directly for both product managers and engineers, supporting them in defining feature specifications and implementation plans through a structured documentation framework.

Do I need codebase context to define feature specifications?

Yes, you need codebase context to accurately define feature specifications, as accessing existing codebase logic ensures the generated design document and task breakdowns are technically viable.