skills.rest
samwelmunga
samwelmungaCOMMUNITY
Explore all skills by this author →
GitHub

init-with-template

Generate and update epic definitions in a structured project summary file.

Updated Aug 27, 2026
Search Tags:#workflow#planning#scaffold#epics#scrum#project-management
One-click install
npx skills add https://github.com/samwelmunga/JengaAgent --skill init-with-template
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-with-template
Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/init-with-template
Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill init-with-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill eliminates the ambiguity of project planning by providing a structured framework for defining epics and stories, ensuring that project goals are clearly documented and tracked from inception.

Core Features & Use Cases

  • Epic Definition: Automatically scaffolds project epics using a standardized JSON schema to ensure consistency across the development lifecycle.
  • Contextual Planning: Integrates with existing project summaries to allow for seamless expansion of new feature areas without duplicating work.
  • Use Case: When starting a new REST API project, use this skill to define the initial epics for authentication, rate limiting, and dashboarding, ensuring each has a clear purpose and tracking status.

Quick Start

Use the init-with-template skill to define a new epic for the user authentication feature area in the current project.

Frequently Asked Questions about init-with-template

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

FAQPage Schema
How do I scaffold project epics and feature areas for a new REST API?▼

You can scaffold project epics by using a standardized JSON schema to define feature areas like authentication or rate limiting, ensuring each epic has a clear purpose and tracking status within your project summary file.

What is the best way to standardize epic definitions for scrum project management?▼

Standardizing epic definitions involves generating and updating structured JSON objects within a project summary file. This framework ensures project goals are clearly documented and tracked from inception through the development lifecycle.

How does automated epic planning integrate with existing project summaries?▼

Automated epic planning integrates with existing project summaries by reading and writing to your project directory. This allows seamless expansion of new feature areas without duplicating previous planning work.

Can I use markdown-based story templates alongside JSON epic definitions?▼

Yes, the project planning process utilizes both JSON-based epic objects for structured tracking and markdown-based story templates for detailed documentation, requiring directory access to read and write these files.

How do I plan development phases using a role-based interaction model?▼

You can plan development phases through a guided, role-based interaction model that facilitates the creation of new feature areas and updates existing epic definitions within your structured project summary file.

Related Skills

Explore More Product & Management Skills→
ioniksioniks
526

markdown-task-manager

Turn local Markdown files into a live Kanban board.

Community
Basic
geekdesign27geekdesign27

bmad-sprint-planning

Generate sprint-status.yaml files from epic markdown definitions.

Community
Intermediate
ImaginerLabsImaginerLabs

bmad-sprint-planning

Generate sprint-status.yaml from epic and story markdown files.

Official
Advanced
skilluseskilluse
55

epic

Create and organize project epics with markdown files for progress tracking.

Official
Intermediate