brownfield-create-story

Consolidate scattered documentation into implementation-ready stories with acceptance criteria and risk assessments.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill brownfield-create-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brownfield-create-story
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/story/brownfield-create-story
Command: npx skills add https://github.com/GDSDN/kord-aios --skill brownfield-create-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill bridges the gap between non-standard documentation formats in brownfield projects and executable development stories, ensuring clarity and safety for implementation.

Core Features & Use Cases

  • Context Gathering: Consolidates information from various sources like brownfield PRDs, epics, and user input.
  • Story Structuring: Creates detailed, implementation-ready stories with acceptance criteria and tasks.
  • Risk Assessment: Identifies and mitigates risks specific to brownfield development.
  • Use Case: You're working on a legacy system with scattered technical notes. This Skill helps you consolidate those notes into a clear story for a new feature, including checks to ensure existing functionality isn't broken.

Quick Start

Use the brownfield-create-story skill to create a new story from the document 'legacy-system-notes.md'.

Frequently Asked Questions about brownfield-create-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create implementation stories for legacy systems without standardized PRDs?

You can generate implementation-ready stories for legacy systems by consolidating scattered technical notes and documentation. This process defines acceptance criteria, technical context, and task breakdowns to bridge documentation gaps in brownfield projects.

What is the best way to assess integration risks when adding features to brownfield projects?

Assessing integration risks in brownfield projects requires identifying and mitigating threats to existing system stability during story creation. This ensures new features include specific checks so existing functionality is not broken by development.

How do I consolidate scattered technical notes into a structured development workflow?

Consolidating scattered technical notes into a development workflow involves gathering context from various sources like brownfield PRDs and epics. This structures the information into detailed, implementation-ready stories with clear tasks and acceptance criteria.

Can I use existing documentation like epics and user input to generate stories for brownfield development?

Yes, you can use existing documentation like brownfield PRDs, epics, and user input to generate stories. The skill consolidates these disparate sources to produce detailed, implementation-ready stories with risk assessments and task breakdowns.

What limitations should I expect when creating stories for legacy systems lacking architecture documents?

When creating stories for legacy systems lacking architecture documents, you face challenges in ensuring integration safety and existing system stability. The skill mitigates these limitations by focusing on risk assessments and comprehensive task breakdowns.