Project Workflow

SkillDev tools

Nine integrated slash commands for complete project lifecycle: /explore-idea, /plan-project, /plan-feature, /wrap-session, /continue-session, /workflow, /release, /brief, /reflect.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Project Workflow skill

What this skill tells your AI

The instructions your AI receives, as published by dennislee928/ethic-latex in .claude/skills/project-workflow/SKILL.md and read by ahel’s review.

One sentence

One ask → the right steps in order → three files on disk + a short chat summary.

Pick a path first (routing)

User means…Run
New folder / “what is this?” / guide onlyStep 1 only → explain-new-project
“Worth my time?” / build vs buyStep 2 → project-worth-my-time (read PROJECT_GUIDE.md first if it exists)
“I’m back after a while” / what’s newStep 3 → project-catch-up
“Full workflow” / “check-in” / “do everything”Steps 1 → 2 → 3 in order (unless skip rules below)
UnclearDefault: full (1 → 2 → 3)

Same audience as the other skills: self-taught, plain language, Learn: for jargon.

What each step saves

StepSkillFile
1explain-new-projectPROJECT_GUIDE.md
2project-worth-my-timePROJECT_VERDICT.md
3project-catch-upPROJECT_CATCH_UP.md

Before you start

  1. Confirm project root (workspace folder or path user names).
  2. Glance at which PROJECT_*.md files already exist—report in chat, then follow skip rules or user request.

Execute

For each step you run: read that skill’s SKILL.md and follow it completely (do not shorten sub-skills).

  • Step 2 uses Pieces MCP (user-pieces: get_user_persona, ask_pieces_ltm) when available.
  • Step 3 uses web search when available.

Do not ask permission to save files—sub-skills always save.

Skip rules

User saysSkip
guide only / step 1 only2 and 3
no verdict / no worth2
no catch-up3
verdict only1 if PROJECT_GUIDE.md exists and is usable; else run 1 first
catch-up only1 if guide missing; else skip 1 and 2
File already existsDefault
All three fresh enoughAsk once: Re-run all three or only what’s missing? If user said full workflow, re-run all (overwrite).
User said full workflowOverwrite all three

After you finish — chat reply (keep short)

Use this checklist in the reply:

Done:
- [ ] PROJECT_GUIDE.md — paste "In one minute" + "How you run it"
- [ ] PROJECT_VERDICT.md — paste Quick verdict + What I'd do (if ran step 2)
- [ ] PROJECT_CATCH_UP.md — paste Headline + Do these first (if ran step 3)

Files saved at: [project root path]

If a step was skipped, say which and why.

Prerequisites

NeedFor
Write access to project rootAll steps
PiecesOS + the pieces MCP server configured in your agentStep 2 (ok to skip Pieces if down—say so)
Web searchStep 3

What not to do

  • Do not inline the full text of the three skills—delegate to them.
  • Do not run step 2 or 3 without project context (guide or quick explore per sub-skill).
  • Do not add a fourth combined markdown file.

Related

  • The Pieces MCP server name can differ between agents (often pieces or user-pieces). Use whichever name your coding agent exposes; the flow is identical.

Signals

GitHub stars
53
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
project-workflow
Source
github.com/dennislee928/ethic-latex