AGENT SKILL

x-story-create

Create focused Story artifacts from an existing Feature markdown with epic linkage, sourceFeature metadata, inherited RNFs, and Product-First streamlined sections.

License 许可
MIT
最近更新
2026-10-27
Stars
★ 0
Forks
1

01 前言 Front Matter

name
x-story-create
model
sonnet
description
Create focused Story artifacts from an existing Feature markdown with epic linkage, sourceFeature metadata, inherited RNFs, and Product-First streamlined sections.
allowed-tools
Read, Write, Edit, Bash, Grep, Glob, Skill
argument-hint
--from-feature <feature-file|feature-id> --epic-id <EPIC-NNNN|NNNN> [--capability-file <path>] [--product-file <path>] [--output-dir <path>] [--dry-run]
context-budget
light
user-invocable
true
requires-capabilities
[]

03 SKILL.md 正文

Output Policy

  • Language: Portuguese (pt-BR) for all content. English only for code identifiers and established technical terms.
  • Tone: Technical, Direct, and Concise.
  • Efficiency: Avoid repeating Product-First rationale already captured in parent artifacts.

Skill: x-story-create

Purpose

Generate 1-N Story markdown artifacts from an existing Feature artifact, linked to a target epic via --epic-id. This focused Product-First wrapper materializes only the Feature → Story step, preserving sourceFeature, carrying inherited RNFs into ## 2. RNFs Herdadas, and intentionally omitting the generic sections 4 and 8 plus the default 2. Persona & Cenário because that context is already represented upstream.

EPIC-0077 semantic reintroduction: x-story-create was hard-cut in EPIC-0065 when generic story generation moved behind x-internal-create-story. It is reintroduced here with a narrower responsibility: Feature-derived story generation only. It is not a legacy alias.

When to Use

  • You already have a Feature artifact and need the derived Stories only
  • You want to bind generated stories to an existing epic via --epic-id
  • You need inherited RNFs rendered explicitly into the story markdown before implementation starts

Prerequisites

Read before starting:

  • .claude/templates/_TEMPLATE-STORY.md
  • .claude/skills/planning-standards-kp/SKILL.md — mandatory RA9 source of truth
  • .claude/skills/x-internal-create-story/SKILL.md

If the feature source cannot be resolved, stop with a validation error.

Workflow

  1. Resolve --from-feature:
    • if it is a file path, use it directly;
    • otherwise, resolve it by feature id under ai/**.
  2. Normalize --epic-id (EPIC-NNNN or NNNN → NNNN).
  3. Resolve optional --capability-file and --product-file for RNF inheritance.
  4. Decompose the feature into 1-N stories using its use cases as story seeds.
  5. Create ai/epics/epic-<ID>-<slug>/story-<ID>-<NNNN>.md.
  6. Populate:
    • Epic ID
    • Source Feature
    • Source Feature Link
    • ## 2. RNFs Herdadas
    • ## 1, ## 3, ## 5, ## 6, ## 7, ## 9
  7. Do not render ## 2. Persona & Cenário, ## 4. AC (Gherkin ...), or ## 8. Decision Rationale for these Feature-derived stories.

Parameters

Parameter Required Description
--from-feature <feature-file|feature-id> Yes Feature markdown source
--epic-id <EPIC-NNNN|NNNN> Yes Epic identifier to link generated stories
--capability-file <path> No Capability markdown used to enrich inherited RNFs
--product-file <path> No Product markdown used to extend inherited RNFs
--output-dir <path> No Base output dir (default ai/epics)
--dry-run No Validate inputs without writing files

Integration Notes

  • x-create-feature remains the full orchestrator for Feature → Epic + Stories + Map.
  • x-story-create is the focused public wrapper for Feature → Story only.
  • x-internal-create-story remains the reusable internal implementation surface for orchestrators and focused wrappers.

04 同仓库更多 Skills

review-bench
review-bench/edercnj_ia-dev-environment

x-parallel-eval

Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.

★ 0
review-bench
review-bench/edercnj_ia-dev-environment

parallelism-heuristics

Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard / regen / soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.

★ 0
review-bench
review-bench/edercnj_ia-dev-environment

x-watch-pr-ci

Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.

★ 0
review-bench
review-bench/edercnj_ia-dev-environment

x-validate-docs

Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.

★ 0
review-bench
review-bench/edercnj_ia-dev-environment

x-update-system-architecture

Incrementally updates docs/architecture/system.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.

★ 0
review-bench
review-bench/edercnj_ia-dev-environment

x-update-architecture

Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.

★ 0