Skip to content

strategy-refine

Refines exactly one strategy per invocation — adding the technical approach, affected components, impacted teams, high-level requirements, dependencies, non-functional requirements, out-of-scope, acceptance criteria, effort estimate, risks, assumptions, and open questions using the unified strat-template.md. It grounds the how in the platform's architecture context and follows a strict priority chain of HOW inputs: Staff Engineer / SME Input > architecture-context overlays > removed RFE implementation context (from source-RFE comments) > generated architecture docs. In revision mode (a prior review exists) it addresses each reviewer's concerns rather than regenerating from scratch. It only ever writes the ## Strategy section, updates frontmatter to Refined, and (outside dry-run) pushes the section to Jira with a provenance label.

Plugin: strat-creator | User-invocable

Contract

Skill Contract canonical-skill-v1

Refine a strategy stub into a complete strategy with technical approach, dependencies, impacted teams, and NFRs.

Identity

Functions
transform
Success
  • Produces a refined strategy with HOW, dependencies, and NFRs grounded in platform architecture.
  • Updates the local strategy artifact with complete frontmatter and structured sections.

Optimization Targets

task_success judge SKILL.md @ 0e102d4

Invariants

Must Preserve
  • Do not alter the original RFE scope or acceptance criteria.
  • Do not fabricate component names or dependencies not present in the architecture context.
Fixed Context
toolsRead, Write, Edit, Glob, Grep, Bash
clipython3
knowledgerepository_contentpublic, task_inputtask_private, tool_outputtask_private

Traceability

Skill
.claude/skills/strategy-refine/SKILL.md
Supporting

Diagram

strategy-refine diagram

Arguments

/strategy-refine <RHAISTRAT-NNNN> [--dry-run] [--architecture-context <path>]
Argument Required Default Description
RHAISTRAT-NNNN - The strategy key to refine (e.g. RHAISTRAT-1531 or STRAT-001). Exactly one per invocation; the skill errors without it.
--architecture-context - Local path to an architecture-context checkout to link instead of fetching from remote — useful for testing overlay changes locally.
--dry-run - Skip all Jira writes (no push, no labels). Reads and local artifact updates still happen.

Usage

/strategy-refine RHAISTRAT-1531
/strategy-refine RHAISTRAT-1531 --dry-run
/strategy-refine RHAISTRAT-1531 --architecture-context ../architecture-context