play-story

Fetch GitHub Projects tasks and gather requirements, context, and ADRs.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill play-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: play-story
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/github%3Astory-play
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill play-story

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire process of preparing a new development story, from fetching it to gathering all necessary context and documentation, ensuring developers can start coding immediately with full clarity.

Core Features & Use Cases

  • Automated Story Fetching: Retrieves the next prioritized story from GitHub Projects.
  • Context Gathering: Collects Non-Functional Requirements (NFRs), technical context, and relevant documentation.
  • ADR Creation: Conditionally creates Architecture Decision Records for new implementations.
  • Use Case: A developer starting their day can run /play-story to get the next task, understand its requirements, review related code and docs, and have an ADR ready, all before writing a single line of code.

Quick Start

Run the play-story skill to prepare the next development task.

Frequently Asked Questions about play-story

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

FAQPage Schema
How do I automate development story preparation from GitHub Projects?

Automated development story preparation fetches prioritized tasks from GitHub Projects, gathers non-functional requirements, collects technical context, and conditionally generates Architecture Decision Records to ensure coding readiness.

What is included in context gathering for a new development story?

Context gathering for a development story includes collecting non-functional requirements, retrieving relevant technical context, and reviewing related documentation to provide full clarity before implementation begins.

How do I automatically create an Architecture Decision Record for a new story?

Automated Architecture Decision Record creation conditionally triggers during story preparation, documenting architectural choices for new implementations before development starts.

Does this story preparation workflow integrate with other context gathering tools?

The story preparation workflow integrates with helper skills like fetch-story, gather-nfr, gather-context, and create-adr to orchestrate a comprehensive multi-step preparation process.

Can I prepare non-functional requirements and technical context in a single workflow?

Yes, you can prepare non-functional requirements and technical context in a single workflow that orchestrates multi-step context gathering and documentation generation for development stories.

What are the limitations of automated story orchestration for development preparation?

Automated story orchestration limitations depend on GitHub Projects integration availability and the conditional nature of Architecture Decision Record creation, which only triggers for specific new implementation scenarios.