agentleFS
Sign inStart free
samwelmungasamwelmunga/jenga-npm/.agents/skills/j-proceed/SKILL.md

j.proceed

Skill0 starsChanged 22 days agoApache-2.0View on GitHub

Review project progress by checking epics and stories, optionally consulting PROJECT_SUMMARY.md and WARP.md, then continue executing the project plan.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If there are tasks in Pending or In Progress status that have not yet been assigned to the developer, identify them.

    line 31
  2. Very specific:

    If outstanding tasks are ready for implementation, write a session handoff to …

    line 32
  3. Distinctive:

    If all tasks are complete, check for epic/story rollup and update board statuses accordingly.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Proceed — Resume Project Execution

skills/j-proceed/ is the canonical, hand-edited directory for this skill, per CLAUDE.md's "The Canonical Naming Contract" (the E50 reopening of 2026-09-09, which promoted skills/j-proceed/ from generated twin to sole canonical form). The j- prefix is there for collision safety — a real directory under a distinct name, so a host tool shipping its own same-named built-in command cannot shadow it (Claude Code's native skill resolution is a literal-string, directory-name-based match; see project/documentation/skill-authoring.md's "Invocation Convention").

⚠️ scripts/generate-j-alias.sh was retired by E50_S14 and no longer exists — there is nothing to run. This file was previously generated from a bare skills/proceed/SKILL.md source; E50_S15 deleted that directory. This file is now the sole canonical, hand-edited source for this skill — edit it directly.

Instructions

  1. Assess progress — Read project/PROJECT_SUMMARY.md, then check project/board/epics/, project/board/stories/, and project/board/tasks/ to determine how far the project has come and what is outstanding.
  2. Check queues — Review project/queue/scrum_triggers.jsonl for any pending triggers (rollup reviews, rapport reviews, status reviews). Process them first before deciding on next steps.
  3. Determine the next action:
    • If there are tasks in Pending or In Progress status that have not yet been assigned to the developer, identify them.
    • If outstanding tasks are ready for implementation, write a session handoff to project/queue/handoffs/scrum-master-<session_id>-<task_id>.json (per-session path — see $([ -f templates/SCRUM_BOARD_SCHEMA.md ] && echo templates/SCRUM_BOARD_SCHEMA.md || echo node_modules/@jenga-ai/agent/templates/SCRUM_BOARD_SCHEMA.md)'s handoffs/ section; use the first task ID, or batch if several) with "status": "planning_complete" so that on_session_end.sh routes them to the developer queue.
    • If all tasks are complete, check for epic/story rollup and update board statuses accordingly.
  4. Report a clear summary to the user: what is done, what is in progress, what is next — and which agent will handle it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free