Analyze project documentation and task hierarchies to identify the next actionable task.
npx skills add https://github.com/samwelmunga/JengaAgent --skill continue-samwelmunga
Please help me install this Agent Skill. Skill: continue Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/continue Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill continue-samwelmunga
This skill eliminates the ambiguity of session-based development by providing a clear, automated audit of project progress across summaries, epics, and stories.
Run the continue skill to analyze the current project state and identify the next pending task.
High-intent search queries and answers about installing and using this skill.
To identify the next actionable task, analyze project-level documentation, epics, and stories to evaluate development progress. This process audits incomplete work items across the project board, highlighting pending stories to facilitate seamless context switching when you resume work.
Tracking project status across epics and stories involves aggregating updates from project summaries and individual work items. This provides a unified view of completion, ensuring work-in-progress items are prioritized and preventing tasks from being forgotten between development sessions.
Context switching works by analyzing the existing project board state to report the next pending task. It evaluates progress across summaries, epics, and stories to automatically audit development progress, eliminating ambiguity and instantly identifying incomplete work items.
Yes, you can use project documentation to find pending tasks by analyzing task hierarchies and project summaries. This evaluates the current state of development across epics and stories to identify incomplete work items and report the next actionable task.
You need project-level documentation containing summaries, epics, and stories to identify incomplete work items. The skill analyzes this existing task hierarchy to evaluate progress and determine the current state of development without requiring additional dependencies.
levnikolaevichDecompose Epics into 5-10 User Stories with sequential numbering.
i3ringitManage Markdown todo files with YAML frontmatter in the todos/ directory.
bresillaOrganize work as a hierarchical graph of epics and tasks.
Asher-PlihalCapture git and project state into HANDOFF.md and claude-progress.txt.
