Files
fidelity-ai-workspace/.opencode/commands/story-draft.md
david.delagneau 374991a568 Refactor workspace structure and documentation
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
2026-04-16 16:28:30 -06:00

2.7 KiB

description
description
Draft a Jira story proposal with Fidelity-ready context and acceptance criteria

Draft a future Jira story from rough notes, findings, or follow-up ideas.

This command should optimize for:

  • professional story wording
  • explicit scope
  • useful acceptance criteria
  • clear ownership framing
  • natural US English that the current manager or stakeholder can reuse or forward without rewriting

Input notes or rough idea:

$ARGUMENTS

Read:

@core/README.md @core/memory/operational-memory.md @prompts/story-draft.md @vault/01-current/current-work.md @vault/01-current/work-items.md @vault/03-context/project.md @vault/03-context/workstreams/index.md @vault/03-context/process/communication.md @vault/03-context/process/jira-story-rules.md @vault/04-people/manager.md @vault/04-people/index.md

Today's log, if present:

!if [ -f vault/06-daily/$(date +%F).md ]; then cat vault/06-daily/$(date +%F).md; else echo "No daily note exists for today yet."; fi

Latest Mattermost context, if available:

!if [ -s ai/inbox/mattermost-latest.md ]; then cat ai/inbox/mattermost-latest.md; elif [ -s scripts/mattermost/generated/mattermost_context.jsonl ]; then cat scripts/mattermost/generated/mattermost_context.jsonl; else echo "No Mattermost context available."; fi

Detailed active work item files, if available:

!if [ -d vault/02-work-items ]; then for f in vault/02-work-items/*.md; do case "$f" in *README.md|*index.md) continue;; esac; echo "\n### $f"; cat "$f"; done; else echo "No work item files available."; fi

Requirements:

  • Use professional-communication when available.
  • Preserve the exact technical meaning of the input
  • Rewrite fully when needed so the output sounds like a fluent senior engineer wrote it
  • Choose the most appropriate story framing: bug, enhancement, spike, task, or follow-up
  • Keep the title short, concrete, and Jira-ready
  • Make the description specific enough that another engineer can understand the intended work
  • Separate current problem, root-cause suspicion, workaround, and follow-up work when relevant
  • Do not overstate certainty; if something is still a hypothesis, label it clearly
  • Make ownership explicit when helpful: XFlow vs consumer app vs service/configuration vs other framework
  • Acceptance criteria should be testable and scoped to the proposed story
  • If the story looks too large or too ambiguous, say so explicitly and suggest spike framing instead
  • If useful, include a short note about dependencies, blockers, or coordination needed
  • If the story touches consumer validation or release propagation, reflect that explicitly in the description or notes

Return:

  1. Suggested story type
  2. Jira-ready title
  3. Description
  4. Acceptance criteria
  5. Optional notes on dependencies / blockers / sizing concerns