idea-refine

Refines vague ideas into structured proposals through divergent and convergent thinking phases.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill idea-refine-rkaaaa404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/Rkaaaa404/cyberhack-SYDT/tree/main/.agents/skills/idea-refine
Command: npx skills add https://github.com/Rkaaaa404/cyberhack-SYDT --skill idea-refine-rkaaaa404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into building features based on vague concepts like "I want a dashboard", leading to wrong assumptions, unbounded scope, and wasted effort. This Skill structures the exploration of rough ideas into clear, validated proposals before any specification or code is written. ## Core Features & Use Cases - Divergent Exploration: Asks ten structured questions across the problem space and solution space to surface users, constraints, prior art, and failure modes. - Convergent Proposal: Narrows findings into a concrete proposal with problem statement, target users, key features, explicit out-of-scope items, and success metrics. - DaaS Platform Check: Maps idea requirements against built-in DaaS capabilities (audit logging, workflows, versioning, RBAC, cron, scopes) so existing platform features are configured rather than rebuilt. - Use Case: A stakeholder says "we need better lot tracking". Use this Skill to explore the actual pain point, compare three approaches, confirm DaaS activity logging already covers part of it, and produce a bounded proposal ready for specification. ## Quick Start Ask the assistant to refine your rough feature idea using the idea-refine process before writing any specification.

Frequently Asked Questions about idea-refine

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

FAQPage Schema
How do I turn a vague feature idea into a concrete proposal?▼

Use a two-phase refinement process: first diverge by asking ten questions about the problem space and solution space, then converge into a proposal with a problem statement, target users, key features, out-of-scope items, and a success metric.

What questions should I ask before writing a product specification?▼

Ask what problem is being solved, who has it, how it is solved today, what happens if unsolved, and what good enough looks like. Then explore three approaches, their trade-offs, prior art, constraints, and failure modes.

When should I not use idea refinement?▼

Skip refinement when requirements are already clear and specific. In that case, go directly to specification with a spec-driven-development workflow instead of re-exploring the problem space.

How do I avoid rebuilding features that DaaS already provides?▼

Check the DaaS capability table before refining data-centric ideas. DaaS includes audit logging, workflow state machines, versioning, files API, cron jobs, RBAC, scopes, and import/export utilities, so refinement should focus on configuration and presentation.

What makes an idea proposal ready for specification?▼

A proposal is ready when the problem statement is specific, target users are identified, at least two alternatives were considered and rejected with reasons, DaaS overlap was checked, and scope boundaries are explicit.