Ideas

Ideas is a quick-capture system for turning rough thoughts into structured work. You write a one-liner, JuhJuh expands it into a full product requirements document, and then converts it into tickets your team can execute immediately.

Capturing an idea¶

Open any project and click Ideas in the sidebar. Click New Idea to start.

An idea needs a title. Everything else is optional but improves expansion quality.

Tip: Be specific. "Add rate limiting to the public API with sliding window and per-org quotas" produces a sharper expansion than "add rate limiting."

You can also include @juhjuh directives in the content field. These become high-priority constraints during expansion and PRD generation. For example: @juhjuh must support both REST and GraphQL endpoints.

Idea lifecycle¶

Every idea moves through five statuses in order.

stateDiagram-v2
    [*] --> Draft
    Draft --> Expanding: Expand
    Expanding --> Refined: AI completes
    Expanding --> Draft: Error
    Refined --> Converting: Convert to tickets
    Converting --> Converted: Tickets created
    Converting --> Refined: Error
    Converted --> [*]

Draft¶

The initial state after creation. You can edit the title, content, and tags freely. This is where you refine your raw thought before asking AI to expand it.

Expanding¶

AI is generating a detailed expansion of your idea. The idea is locked during this phase; you cannot edit it until expansion finishes. If something goes wrong, the idea reverts to Draft with an error note in its metadata.

Refined¶

Expansion is complete. You now have an AI-generated requirements breakdown alongside your original content. Review the expansion, adjust your content if needed, and either re-expand with new instructions or move to conversion.

You can also start a brainstorm session at this point to refine the idea further before converting.

Converting¶

JuhJuh is generating a PRD and parsing it into individual tickets. This is a multi-step process that typically takes a minute or two. The idea is locked during conversion.

Converted¶

Tickets have been created in your project. Each ticket links back to this idea as its source. The idea itself is now read-only, serving as an archive of the original concept and the PRD that produced the tickets.

Expanding an idea¶

From the idea detail page, click Expand. JuhJuh sends your title, content, and any @juhjuh directives to an AI model that generates a structured requirements expansion.

The expansion covers:

• Problem statement and user impact
• Functional requirements broken into clear items
• Technical considerations and constraints
• Edge cases and potential risks
• Suggested acceptance criteria

If the expansion does not match what you had in mind, update your content with more context and click Expand again. You can re-expand as many times as you need. Each expansion replaces the previous one.

Brainstorming¶

Brainstorm is an interactive session where six AI team members discuss your idea in real time. It is available once an idea reaches the Refined status.

The team¶

How a session works¶

1. Click Brainstorm on the idea detail page.
2. Cadence (PM Lead) opens the session with a discovery question based on your idea.
3. You respond with answers, preferences, or follow-up questions.
4. The team members respond. Cadence routes your messages to the right experts and coordinates responses.
5. The session moves through phases: discovery (understanding the problem), recap (confirming the direction), and brainstorm (detailing the solution).
6. When you are satisfied, click End Session. JuhJuh generates a recap proposal summarizing key decisions.
7. Review and approve the recap. Each team member posts a farewell, and the session summary is saved to the idea.

Brainstorm sessions run over WebSocket, so responses stream in real time. You see typing indicators as each agent formulates their response.

Rate limit: 5 messages per 60 seconds during a brainstorm session.

Converting to tickets¶

Once your idea is in the Refined state, click Convert to Tickets. This triggers a three-stage process.

Stage 1: PRD generation¶

JuhJuh generates a full product requirements document from your title, content, AI expansion, brainstorm summary (if any), and project knowledge. The PRD includes:

• Problem statement
• Scope boundaries (what is in and out)
• Functional requirements
• Non-functional requirements (performance, security, accessibility)
• Technical architecture recommendations
• Testing strategy
• Risk assessment

The PRD is stored on the idea and viewable from the detail page under PRD Overview.

Stage 2: Ticket parsing¶

JuhJuh reads the PRD and breaks it into discrete, actionable tickets. Each ticket gets a title, description, issue type (Epic, Story, Bug, or Task), and priority based on the PRD content.

Stage 3: Ticket creation¶

The parsed tickets are created in your project with their source marked as AI-generated and linked back to the originating idea. They appear on your board immediately.

After conversion, you can view all generated tickets from the idea detail page and adjust priorities, descriptions, or assignments as needed.

Viewing the PRD¶

After conversion, the PRD is accessible from the idea detail page. Click PRD Overview to see the full document, or click into individual sections for focused reading.

PRD sections include cross-references to related requirements, so you can trace how high-level goals connect to specific tickets.

Permissions¶

Idea access follows project permissions.

API access¶

Ideas are available through the REST API.

Filtering¶

Expand and convert operations are triggered through the dashboard or via Slack and gateway intents, not through the REST API directly.

Tips for better results¶

• Start specific. "Add OAuth2 with PKCE flow for the mobile app" beats "add login."
• Use @juhjuh directives. They carry extra weight during expansion. Use them for hard constraints: @juhjuh must not break the existing session-based auth.
• Include context in the content field. Reference existing features, link to designs, or describe the user workflow. More input means a sharper PRD.
• Brainstorm before converting. The brainstorm summary feeds into PRD generation. A 5-minute session with the virtual team often catches gaps that save hours later.
• Re-expand if needed. If the first expansion misses the mark, add clarifying details to your content and expand again. There is no penalty for multiple expansions.

Related¶

• Tickets, the actionable work items generated from your ideas
• Projects, where ideas live alongside tickets, boards, and configuration
• Agents, the AI runners that execute the tickets your ideas produce
• Boards, visualize and prioritize the tickets generated from ideas
• Automation, auto-classification and triaging for converted tickets
• Prompts, the templates that shape how PRDs and expansions are generated