skills.rest
gautam-achieveai
gautam-achieveaiCOMMUNITY
Explore all skills by this author →
GitHub

draft-feature

Develop deep software feature requirements through context analysis and blind-spot detection.

2|Updated Apr 12, 2026
Search Tags:#codebase analysis#structured development#feature requirements#blind-spot detection#over-engineering review
One-click install
npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill draft-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-feature
Source: https://github.com/gautam-achieveai/ClaudePlugins/tree/main/development/skills/draft-feature
Command: npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill draft-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The draft-feature Skill resolves the challenge of creating comprehensive and actionable requirements for new features or user stories, ensuring clarity and completeness from initial idea to documented work item.

Core Features & Use Cases

  • Structured Requirements Development: Provides a structured 8-phase workflow to turn rough feature ideas into well-defined, reviewed work items.
  • Codebase and Prior Art Analysis: Integrates codebase exploration and prior art searches to ensure feature context and prevent duplicate efforts.
  • Blind-Spot Detection: Utilizes specialized agents to uncover unconsidered aspects, such as edge cases, security, and performance implications.
  • Over-Engineering and Duplication Review: Ensures that requirements are not over-engineered and that no existing functionality is duplicated.

Quick Start

Use the draft-feature Skill to draft a feature: "Implement a customer loyalty program that provides points for purchases."

Frequently Asked Questions about draft-feature

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

FAQPage Schema
How do I write structured feature requirements from a rough idea?▼

Feature requirements blind-spot detection uses specialized agents to uncover unconsidered edge cases, security vulnerabilities, and performance implications during the design phase.

How do I prevent over-engineering and duplication when planning new software features?▼

To prevent over-engineering and duplication when planning new software features, review requirements against existing codebase prior art to ensure functionality is not unnecessarily complex or repeated.

What is the best way to analyze a codebase for prior art before implementing a feature?▼

The best way to analyze a codebase for prior art is to integrate codebase exploration within the feature drafting workflow to ensure context and prevent duplicate development efforts.

Can I draft a feature work item without providing structured input text?▼

No, drafting a feature work item requires structured input with a provider, user-provided text, and previous responses to run its clarification loops and agent-based detection correctly.

What are the limitations of automated feature requirements generation?▼

Automated feature requirements generation requires structured input and relies on clarification loops, meaning it cannot function effectively without user-provided text and prior response context to detect blind spots.

Related Skills

Explore More Software Engineering Skills→
tjesperstjespers
1

speckit-refine

Identify feature spec gaps and generate /speckit.clarify prompts.

Community
Advanced
foolpoet44foolpoet44
1

userstory-documentation

Translate PRDs into epics, user stories, and acceptance criteria.

Community
Advanced
timequitytimequity
6

beads-validation

Validate beads issues for PRD mapping, dependencies, readiness, and priorities.

Official
Advanced
buddypiabuddypia

feature-architect

Generate technical specifications and documentation from user stories and requirements.

Community
Advanced