core

Coordinate sprint planning and task tracking using prd.json and native Tasks.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/djnsty23/claude-auto-dev --skill core-djnsty23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core
Source: https://github.com/djnsty23/claude-auto-dev/tree/main/skills/core
Command: npx skills add https://github.com/djnsty23/claude-auto-dev --skill core-djnsty23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

prd.json-driven sprint planning and a hybrid task system enable teams to define, track, and auto-load sprint state via a centralized prd.json, reducing manual coordination.

Core Features & Use Cases

  • Two-layer workflow: persisting long-term history in prd.json and executing work with native Tasks during sessions.
  • prd.json Story Schema guidance with fields like id, title, passes, type, priority, and resolution, enabling consistent tracking and reporting.
  • Archive and governance guidance: prompts to archive when thresholds are met and move completed stories to archives.

Quick Start

Create or load your prd.json and start managing stories with native Tasks to drive the sprint.

Frequently Asked Questions about core

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

FAQPage Schema
How do I manage sprint planning using prd.json?

Sprint planning with prd.json involves defining and tracking iterative sprints through a centralized file, reducing manual coordination. The system uses a two-layer model where prd.json stores long-term history while native Tasks execute active session work.

What is the story schema for prd.json task management?

The prd.json story schema requires fields including id, title, passes, type, priority, and resolution. This structure enables consistent tracking and reporting across iterative sprints, ensuring each story maintains standardized status fields throughout its lifecycle.

How do I archive completed stories in a prd.json workflow?

Archiving completed stories in a prd.json workflow occurs when defined thresholds are met, moving finished items to archives. This governance guidance prompts you to archive stories systematically, maintaining a clean active sprint backlog.

Can I track sprint tasks with native Tasks alongside prd.json?

You can track sprint tasks with native Tasks alongside prd.json through a two-layer workflow. prd.json persists long-term sprint history while native Tasks execute session work, enabling teams to auto-load sprint state and drive active development simultaneously.

Does prd.json sprint management work for iterative teams with passes?

prd.json sprint management is designed for teams managing iterative sprints with stories and passes. It provides end-to-end guidance from sprint setup through task updates, enforcing story schemas and basic archiving rules for consistent tracking.