Skip to content

feat: add task type distinction (story vs task) in PRD conversion skills#121

Closed
carmandale wants to merge 1 commit intosubsy:mainfrom
carmandale:feat/issue-88-task-type-distinction
Closed

feat: add task type distinction (story vs task) in PRD conversion skills#121
carmandale wants to merge 1 commit intosubsy:mainfrom
carmandale:feat/issue-88-task-type-distinction

Conversation

@carmandale
Copy link
Contributor

@carmandale carmandale commented Jan 17, 2026

Summary

Updates the bundled PRD conversion skills to properly distinguish between user stories and technical tasks, fixing the semantic mismatch where technical work was forced into "user story" format.

Changes

ralph-tui-create-beads

  • Add --type=story for user stories (US-xxx)
  • Add --type=task for functional requirements (FR-xxx → T-xxx)
  • Update conversion rules with FR-xxx to T-xxx mapping
  • Update example to show both story and task types
  • Update labels: stories get ralph,story, tasks get ralph,task

ralph-tui-create-json

  • Add optional type field: "story" or "task"
  • Add T-xxx ID format for technical tasks
  • Update conversion rules for type handling
  • Document type mapping table

Benefits

  • Semantic correctness: Technical tasks aren't forced into awkward "As a developer, I want..." format
  • Better filtering: Filter beads by type (show me all tasks, show me all stories)
  • Clearer PRD structure: Readers understand what's user-facing vs technical
  • Leverages existing capability: beads already supports issue_type
  • Backwards compatible: type field is optional

Example

Before:

bd create --title="US-001: Add investorType field" --description="As a developer, I need..."

After:

bd create --type=task --title="T-001: Add investorType column" --description="Add investorType column..."

Closes #88

Summary by CodeRabbit

Release Notes

  • Documentation
    • Clarified bead creation types with distinct workflows for epics, stories, and tasks.
    • Updated PRD-to-task conversion mapping with explicit functional requirement guidance.
    • Enhanced command examples with type-specific formats and labelling conventions.
    • Improved acceptance criteria specifications with item-type alignment.

✏️ Tip: You can customize this high-level summary in your review settings.

…lls (subsy#88)

Update ralph-tui-create-beads and ralph-tui-create-json skills to support
proper type distinction between user stories and technical tasks:

## Changes

### ralph-tui-create-beads
- Add --type=story for user stories (US-xxx)
- Add --type=task for functional requirements (FR-xxx → T-xxx)
- Update conversion rules with FR-xxx to T-xxx mapping
- Update example to show both story and task types
- Update labels: stories get 'ralph,story', tasks get 'ralph,task'

### ralph-tui-create-json
- Add optional 'type' field: 'story' or 'task'
- Add T-xxx ID format for technical tasks
- Update conversion rules for type handling
- Document type mapping table

## Benefits

- Semantic correctness: technical tasks aren't forced into 'user story' format
- Better filtering: filter beads by type
- Leverages existing beads issue_type capability
- Backwards compatible: type field is optional

Closes subsy#88
@vercel
Copy link

vercel bot commented Jan 17, 2026

@carmandale is attempting to deploy a commit to the plgeek Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 17, 2026

Walkthrough

Documentation updates to two PRD conversion skills introduce explicit type distinctions between user stories (US-xxx) and technical tasks (T-xxx/FR-xxx), adding comprehensive guidance on type-specific creation, mapping rules, acceptance criteria, and labelling conventions with updated examples throughout.

Changes

Cohort / File(s) Summary
Skill Documentation Updates
skills/ralph-tui-create-beads/SKILL.md, skills/ralph-tui-create-json/SKILL.md
Added type distinction framework (stories vs tasks), introduced FR-xxx to T-xxx mapping guidance, updated output examples with type-aware flags (`--type=epic

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Huzzah! The types now dance in harmony—
Tasks and stories, each with clarity!
No more forcing schemas into "As a" frames,
Just T-xxx and US-xxx bearing proper names.
A rabbit's delight: distinction at last! 🌟

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately describes the main change: introducing task type distinction (story vs task) in PRD conversion skills, which aligns with the changeset modifications.
Linked Issues check ✅ Passed The pull request successfully addresses all primary objectives from issue #88: introduces explicit type distinctions (US-xxx/story vs T-xxx/task), adds --type flags to create-beads examples, adds optional type field to create-json schema, provides type-usage guidance, and maintains backwards compatibility.
Out of Scope Changes check ✅ Passed All changes are focused and in-scope: both modified files (create-beads and create-json SKILL.md files) directly address the type distinction objectives outlined in issue #88 with no extraneous modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@subsy
Copy link
Owner

subsy commented Jan 17, 2026

@carmandale this looks to be attempting the same as #95 - worth following along there and reviewing the comments

@subsy
Copy link
Owner

subsy commented Feb 4, 2026

Closing as no longer seeing the need for this

@subsy subsy closed this Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Add task type distinction (story vs task) in PRD conversion skills

2 participants