Skip to content

tsunami28/MindNova / .claude/skills/elaboration-upsert-user-story

elaboration-upsert-user-story

Verified

Create or draft new work items (stories, tasks, bugs, epics) as local markdown files under docs/discovery/, following the house story template, point scale, and conventions. Use this whenever the user wants a new work item: phrasings like "create" or "write up a story", "make a ticket", "log a bug" or "ops task", "create an epic", "raise a ticket", or any description of work that should be tracked as a new item, even when they only describe the work rather than naming a ticket. Do NOT use this for reading, searching, commenting on, transitioning, or reviewing existing tickets; for GitHub issues or pull items, GitHub issues or pull requests, Confluence pages, or PRDs; or for a bare "what points would you give" estimate when there is no ticket to create.

FileKindSize
SKILL.mdskill md6.0 KB
references/story-template.mdmarkdown4.5 KB

references/story-template.md

View on GitHub
# [PLACEHOLDER] Jira Story Template

The AZURE project uses this 6-section markdown template. The emoji headers are house
style and automation keys off them, so keep them exactly as written. Supply a real
description on create so the automation does not overwrite it with a blank default.

## The template

```
πŸ“Œ Background

* [What happened, the current state, why this ticket exists. Reference the originating
  ticket key if this extends prior work.]

🎯 What's the Goal?

* As a [persona],
* I want [capability],
* So that [reason].

πŸ’‘ Expected Value

* [Measurable or concrete impact: faster review, fewer incidents, cost, UX.]

βœ… Success Criteria

* [Conditions that make this done. Make each one checkable, not vague.]

πŸ› οΈ How we'll do it

* [Approach, dependencies, the components touched. Name real files/classes for dev work.]

⚠️ Risks & Blockers

* [What might slow this down, what needs alignment, what is explicitly out of scope.]
```

## Optional: Technical Implementation section

For dev-ready stories (especially MindNova/platform work), add a `πŸ”§ Technical
Implementation` section after `πŸ› οΈ How we'll do it`. List the files reused as-is, the
new/changed components with their paths, the data sources (API methods), and the tests
to add. This is what makes a story pick-up-and-build ready. Cite real symbols, for
example `Services/CloudConfigurationJsonDifferenceService.cs` and the method that does
the work, so the implementer does not have to rediscover them.

## Worked example

This is AZURE-2537, created from this pattern. Note: concrete files and methods in the
technical section, checkable success criteria, explicit out-of-scope, and a points
estimate justified against comparators (5, reusing an existing diff engine and only
adding a version-picker + wiring layer).

```
πŸ“Œ Background

* Today the portal can diff cloud environment configurations, but only a fixed,
  automatic pair: on the configuration page (`CloudConfigurationDetails.razor`), the
  "Configuration Changes Overview (Latest vs New)" panel compares the version being
  viewed against the config derived from its `TemplateConfigurationId`. Built in AZURE-2328.
* The diff engine (`CloudConfigurationJsonDifferenceService.GenerateAlignedDiff`) and the
  viewer (`CloudConfigurationJsonDifferenceViewer`) are already version-agnostic.
* Users have no way to pick two arbitrary versions and compare them. Related: AZURE-2489.

🎯 What's the Goal?

* As a platform admin / cloudspace approver,
* I want to select any two versions of a cloud environment configuration and see the differences,
* So that I can audit how a configuration evolved, not just the auto-selected pair.

πŸ’‘ Expected Value

* Reviewers and auditors can inspect change history on demand.
* Reuses the existing, proven diff rendering, so behaviour stays consistent.

βœ… Success Criteria

* The user can choose a left and a right version from the list of existing versions.
* Selecting two versions renders the existing viewer with the aligned diff of those two.
* Selecting the same version on both sides shows a clear "identical version" empty state.
* The existing automatic "Latest vs New" panel is unaffected.

πŸ› οΈ How we'll do it

* Add a version-selection UI listing versions via `GetCloudEnvironmentConfigurationsAsync`.
* Fetch both configs with `GetCloudEnvironmentConfigurationByIdAsync`, serialize, and call
  `CloudConfigurationJsonDifferenceService.GenerateAlignedDiff(leftJson, rightJson)`.
* Feed the result into `CloudConfigurationJsonDifferenceViewer`.

πŸ”§ Technical Implementation

* Reused as-is: `Services/CloudConfigurationJsonDifferenceService.cs`,
  `CloudConfigurationJsonDifferenceViewer.razor` (+ `.razor.css` / `.razor.js`).
* New: a small `CloudConfigurationVersionCompare.razor` with two pickers, mirroring the
  fetch + serialize + diff wiring in `CloudConfigurationDetails.OnInitializedAsync`.
* Tests (`MindNova/tests/Portal.MindNova.Tests`): picker mapping, same-version short-circuit.

⚠️ Risks & Blockers

* Scope creep on placement (new route + deep-linking + auth) could push 5 toward 8. Keep V1 in-page.
* Overlaps with AZURE-2489; linked as related.
* Out of scope: cross-cloudspace comparison, exporting the diff.
```

## Fields set on creation (for the worked example)

- `issueTypeName`: `Story`
- `projectKey`: `AZURE`
- `additional_fields`: `{"priority": {"name": "Minor"}, "labels": ["MindNova", "Refined"], "customfield_10101": 5, "customfield_10014": "AZURE-2518"}`
- After create: `createIssueLink` (type `Relates`) to the originating story and any placeholder.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product β€” it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product β€” not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial β€” a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK β€” model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER β€” read BEFORE opening the target file; don't skip because it "looks like a one-liner" β€” whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) β€” never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named β€” don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall