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

j.continue

Checks project summary, epics, and stories to determine the next incomplete work item.

Updated Aug 3, 2026
Search Tags:#epics#task tracking#stories#project status#session resume#continue#scrum board
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-continue-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.continue
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-continue
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-continue-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to a project after a session break, it is hard to know exactly where work left off. This Skill inspects the project's Markdown board state and tells you what to do next, or confirms everything is finished. ## Core Features & Use Cases - Hierarchical status check: Reads PROJECT_SUMMARY.md, then epics, then stories to locate outstanding work. - Completion detection: Responds with "All done!" when every epic and story is complete. - Collision-safe invocation: Provides the /j-continue alias so the flow works even when another tool shadows the bare /continue command. - Use Case: You reopen a project after the weekend and ask what to work on; the Skill scans the board and starts the next incomplete story. ## Quick Start Ask the assistant to run j-continue to check the project board and pick up the next incomplete work item.

Frequently Asked Questions about j.continue

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

FAQPage Schema
How do I find out what to work on next in a project?▼

Run the continue flow, which checks PROJECT_SUMMARY.md first, then epics, then stories, and identifies the next incomplete item. If everything is finished it responds with "All done!".

How to resume project work after a session ends?▼

Invoke /j-continue at the start of the new session. It reads the persistent Markdown board state so work survives session boundaries, then begins the next outstanding epic or story automatically.

Why use j-continue instead of the plain continue command?▼

Some host tools have a built-in command named continue that shadows the bare /continue alias. The j-continue directory name provides a collision-safe path to the identical flow.

Does the continue check work if an epic is marked done?▼

Yes. The instructions explicitly require checking story status within an epic even when the epic itself is marked done, so incomplete stories are never skipped.

What files does the continue skill need to work?▼

It requires a project directory containing PROJECT_SUMMARY.md plus epics and stories subdirectories with Markdown files. Without this board structure there is no state to inspect.

Related Skills

Explore More Software Engineering Skills→
jcg-adminjcg-admin

scrum-backlog-refinement

Refines Product Backlogs by splitting epics into INVEST user stories traced to RUP use cases.

Community
Intermediate
TalonT-OrgTalonT-Org
5

implement-worktree-no-merge

Implement a development plan in an isolated Git worktree with phased commits.

Official
Advanced
samwelmungasamwelmunga

reconcile

Synchronize project management board status with git history and documentation artifacts.

Community
Advanced
OmniloyOmniloy

create-jira-work-items

Create Jira feature, development task, and verification issues with duplicate checks.

Official
Advanced