013-agile-feature
From the author
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic; Break down an agile epic into deliverable features. Part of Plinth Toolkit
Install
npx skills add jabrena/plinth --skill 013-agile-feature -a claude-code
Installs to .claude/skills/013-agile-feature/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 86
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- 012-agile-epicjabrena/plinthGuides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth ToolkitWriting★ 455
- 014-agile-user-storyjabrena/plinthGuides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories. Part of Plinth ToolkitWriting★ 455
- feature-planningmhattingpete/claude-skills-marketplaceBreak down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.Planning★ 688
- breakdown-epic-archgithub/awesome-copilotPrompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.Planning★ 40.4K
- speckit-specifyforyourhealth111-pixel/Vibe-SkillsCreate or update feature specifications from natural language descriptions. Use when starting new features or refining requirements. Generates spec.md with user stories, functional requirements, and acceptance criteria following spec-driven development methodology.Planning★ 3.8K
- breakdown-epic-pmgithub/awesome-copilotPrompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.Planning★ 40.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in