Feature Designer

Turn vague feature ideas into formal specifications with iterative requirements and coherence checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tomaslucas/loopy-claude --skill feature-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Feature Designer
Source: https://github.com/tomaslucas/loopy-claude/tree/main/.claude/skills/feature-designer
Command: npx skills add https://github.com/tomaslucas/loopy-claude --skill feature-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns vague feature ideas into formal specifications.

Core Features & Use Cases

  • Iterative Requirements Loop: Guides discovery of goals, non-goals, and edge cases to solidify design.
  • Coherence Validation: Checks consistency with existing specs before crystallization.
  • Batch Crystallization: Generates all related specs in one pass to keep PIN up to date.

Quick Start

To start designing a new feature, say: "design a feature for our search experience" and follow the prompts.

Frequently Asked Questions about Feature Designer

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

FAQPage Schema
How do I turn a vague feature idea into a formal specification?

To turn a vague feature idea into a formal specification, you can use an interactive requirements loop that guides discovery of goals, non-goals, and edge cases to solidify the design.

What is Phase 0 research in feature design and planning?

Phase 0 research in feature design is an enforced preliminary step that gathers necessary context before iterative questioning and plan-generation begin, ensuring the final architecture is well-founded.

How do I check if a new system architecture is coherent with existing specs?

You can check coherence with existing specs by applying a validation step before crystallization, ensuring your new feature design maintains consistency across all current requirements and documentation.

What is the best way to generate multiple related specifications at once?

The best way to generate multiple related specifications at once is through batch crystallization, which produces all associated documents in a single pass to keep your entire spec repository up to date.

When do I need an interactive requirements loop for refining feature requirements?

You need an interactive requirements loop for refining feature requirements when you have vague goals or undefined edge cases, as it iteratively questions your assumptions to solidify the overall system architecture.