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

j.proceed

Reviews board progress and queues pending tasks for developer handoff.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When resuming an AI-assisted development session, the agent has no memory of prior progress, pending tasks, or queued triggers. This Skill restores that context by reading the persistent scrum board and deciding what work should happen next. ## Core Features & Use Cases - Progress Assessment: Reads PROJECT_SUMMARY.md plus epics, stories, and tasks under project/board/ to determine what is done and what remains. - Trigger Queue Processing: Checks project/queue/scrum_triggers.jsonl for pending rollup, rapport, and status reviews before planning next steps. - Developer Handoff: Writes a session handoff JSON with status planning_complete so the on_session_end hook routes pending tasks to the developer agent. - Use Case: After starting a new session mid-project, invoke this Skill to get a summary of completed work, in-progress tasks, and which agent picks up the next task. ## Quick Start Ask the agent to review project progress and continue executing the plan.

Frequently Asked Questions about j.proceed

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

FAQPage Schema
How do I resume an AI agent project after a session ends?▼

Invoke the proceed flow, which reads PROJECT_SUMMARY.md and the board directories to reconstruct project state. It then identifies pending or in-progress tasks and queues them for the developer agent via a handoff file.

How does the scrum master agent hand off tasks to the developer agent?▼

The skill writes a handoff JSON file to project/queue/handoffs/ with status planning_complete, named with the session ID and task ID. The on_session_end.sh hook reads this file and routes the tasks to the developer queue.

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

Some host tools have built-in commands that shadow the bare /proceed alias. The j-proceed directory name provides a collision-safe invocation path with identical behavior, generated from the source skill by a sync script.

What happens when all tasks on the board are complete?▼

The skill checks for epic and story rollups and updates board statuses accordingly. It then reports a summary of what is done, what is in progress, and what comes next.

What are the limitations of board-based progress tracking?▼

Accuracy depends entirely on agents keeping board frontmatter and trigger queues up to date. If statuses are stale or handoff files are malformed, the skill cannot reliably determine the next action.

Related Skills

Explore More Software Engineering Skills→
samwelmungasamwelmunga

status

Aggregate scrum board status from local JSON and Markdown files.

Community
Intermediate
whinchmanwhinchman

coder

Implements features and fixes with test-driven development in isolated git worktrees.

Community
Advanced
StephenTownsend1234StephenTownsend1234

wrap

Save session context and decisions into project files after coding.

Community
Advanced
Dev10x-GuruDev10x-Guru
7

Dev10x:jtbd

Draft Job Stories from GitHub and JIRA issue tracker context.

Official
Advanced