devlyn:ideate

Convert unstructured ideas into VISION.md, ROADMAP.md, and item specs.

4|Updated Feb 23, 2026

Search Tags:#planning #ideation #roadmap #vision #specs #architecture-decisions #auto-resolve

Ready to run

npx skills add https://github.com/fysoul17/one-query-v1 --skill devlyn-ideate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devlyn:ideate
Source: https://github.com/fysoul17/one-query-v1/tree/main/onequery/.claude/skills/devlyn%3Aideate
Command: npx skills add https://github.com/fysoul17/one-query-v1 --skill devlyn-ideate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform unstructured ideas into precise, self-contained planning artifacts (VISION.md, ROADMAP.md, and detailed specs) that feed auto-resolve pipelines.

Core Features & Use Cases

Creates a three-layer output: Vision, Roadmap, and phase-level specs plus architecture decisions; enforces the planning hard boundary to keep ideation separate from implementation.
Supports engine integration (Claude/Codex) for rubric-cross checks and produces human-friendly post-challenge summaries.

Quick Start

Provide a structured ideation prompt and let devlyn produce the full planning package ready for auto-resolve.

Frequently Asked Questions about devlyn:ideate

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

FAQPage Schema

How do I turn unstructured ideas into planning documents for auto-resolve pipelines?▼

You can generate planning documents by providing a structured ideation prompt. The system outputs a three-layer package containing VISION.md, ROADMAP.md, and detailed item specs with architecture decisions, ready for auto-resolve pipelines.

What is the best way to separate ideation from implementation in a roadmap?▼

To separate ideation from implementation, enforce a planning hard boundary. This mechanism isolates the ideation phase to produce self-contained vision and roadmap artifacts before any implementation logic begins.

Does this planning workflow support engine integration for rubric-cross checks?▼

Yes, the planning workflow supports engine integration with Claude or Codex. This enables automated rubric-cross checks during ideation and produces human-friendly post-challenge summaries for the generated specs.

How do I document architecture decisions when creating a project vision and roadmap?▼

To document architecture decisions, define explicit user intent within the ideation session. The system automatically captures these decisions alongside the project vision and phase-level item specs in the output planning artifacts.

Do I need a specific environment to generate phase-level specs and architecture decisions?▼

No specific environment is required beyond the ideation interface. You simply provide a structured ideation prompt, and the system enforces explicit user intent to output phase-level specs and architecture decisions.