nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

feat: AI-assisted PRD / task list creator panel #184

New Issue
Closed
opened 2026-03-06 09:33:01 -08:00 by hikari · 0 comments
hikari commented 2026-03-06 09:33:01 -08:00
Owner
Copy Link
Copy Source

Overview

Inspired by ralph-tui's create-prd command, this adds a PRD Creator Panel — a dedicated UI for breaking down a large feature or goal into a structured list of tasks that can then be fed into the automated task loop.

User Story

As a developer with a large feature to build, I want to describe it in plain English and have Hikari help me break it down into a sequenced list of concrete tasks, so I can review, edit, and then run them autonomously.

Feature Details

How It Works

  1. User opens the PRD Creator Panel
  2. User types a high-level description of what they want to build (e.g. "Add OAuth login with Google and GitHub, including tests and documentation")
  3. Hikari sends the description to Claude with a structured system prompt asking it to produce a numbered task list
  4. Claude returns a breakdown of tasks with titles, prompts, and priorities
  5. User can review, reorder, edit, or delete individual tasks
  6. User clicks "Export" to save as hikari-tasks.json in the current workspace
  7. The task list can immediately be loaded into the Task Loop panel

Panel UI

  • Input area: Multi-line text field for the high-level goal/feature description
  • Context field: Optional additional context (e.g. "We use TypeScript, Vitest for tests, ESLint strict config")
  • Generate button: Sends to Claude and streams the task breakdown
  • Task list editor: Generated tasks displayed as editable cards
    • Title (editable)
    • Prompt/description (editable)
    • Priority (drag to reorder)
    • Delete button per task
    • Add task button for manual entries
  • Export button: Save as hikari-tasks.json
  • Open in Loop button: Directly load into the Task Loop panel (see companion issue)

System Prompt for Task Generation

The panel should use a well-crafted system prompt that instructs Claude to:

  • Break the goal into small, independent, sequenced tasks
  • Write each task prompt in the imperative (e.g. "Write unit tests for...")
  • Assign priorities based on dependencies
  • Keep tasks focused enough for a single Claude Code session

Format Compatibility

Generated hikari-tasks.json should be compatible with the Task Loop panel format from the companion issue.

Acceptance Criteria

  • User can describe a feature and generate a task list with Claude's help
  • Generated tasks are displayed as editable cards
  • User can reorder, edit, and delete tasks before exporting
  • User can manually add tasks
  • Export saves a valid hikari-tasks.json to the workspace root
  • "Open in Loop" button loads the list directly into the Task Loop panel
  • Tests written for all new logic

✨ This issue was created with help from Hikari~ 🌸

## Overview Inspired by [ralph-tui](https://github.com/subsy/ralph-tui)'s `create-prd` command, this adds a **PRD Creator Panel** — a dedicated UI for breaking down a large feature or goal into a structured list of tasks that can then be fed into the automated task loop. ## User Story As a developer with a large feature to build, I want to describe it in plain English and have Hikari help me break it down into a sequenced list of concrete tasks, so I can review, edit, and then run them autonomously. ## Feature Details ### How It Works 1. User opens the PRD Creator Panel 2. User types a high-level description of what they want to build (e.g. "Add OAuth login with Google and GitHub, including tests and documentation") 3. Hikari sends the description to Claude with a structured system prompt asking it to produce a numbered task list 4. Claude returns a breakdown of tasks with titles, prompts, and priorities 5. User can review, reorder, edit, or delete individual tasks 6. User clicks "Export" to save as `hikari-tasks.json` in the current workspace 7. The task list can immediately be loaded into the Task Loop panel ### Panel UI - **Input area**: Multi-line text field for the high-level goal/feature description - **Context field**: Optional additional context (e.g. "We use TypeScript, Vitest for tests, ESLint strict config") - **Generate button**: Sends to Claude and streams the task breakdown - **Task list editor**: Generated tasks displayed as editable cards - Title (editable) - Prompt/description (editable) - Priority (drag to reorder) - Delete button per task - Add task button for manual entries - **Export button**: Save as `hikari-tasks.json` - **Open in Loop button**: Directly load into the Task Loop panel (see companion issue) ### System Prompt for Task Generation The panel should use a well-crafted system prompt that instructs Claude to: - Break the goal into small, independent, sequenced tasks - Write each task prompt in the imperative (e.g. "Write unit tests for...") - Assign priorities based on dependencies - Keep tasks focused enough for a single Claude Code session ### Format Compatibility Generated `hikari-tasks.json` should be compatible with the Task Loop panel format from the companion issue. ## Acceptance Criteria - [ ] User can describe a feature and generate a task list with Claude's help - [ ] Generated tasks are displayed as editable cards - [ ] User can reorder, edit, and delete tasks before exporting - [ ] User can manually add tasks - [ ] Export saves a valid `hikari-tasks.json` to the workspace root - [ ] "Open in Loop" button loads the list directly into the Task Loop panel - [ ] Tests written for all new logic ✨ This issue was created with help from Hikari~ 🌸
naomi closed this issue 2026-03-06 19:35:29 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#184
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?