notque/vexjoy-agent / skills/process/workflow
workflow
VerifiedStructured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
references/pl-pause-extract-decisions.md
View on GitHub# Pause-Work Extract Decisions
Verbatim Phase 3 (EXTRACT DECISIONS) detail. Take the decisions this session made, filter for the ones that warrant ADRs, and draft ADR skeletons for each candidate. This phase runs before WRITE so that ADR data is available for inclusion in both handoff files — passing extracted data downstream is cheaper than appending to files after the fact.
## Step 1: Collect this session's decisions
Use the `decisions` field synthesized in Phase 2, plus any choice made in this session that changed the approach: a tool or library picked over an alternative, a contract fixed between components, a process rule adopted. The session transcript is the source. Record each as one sentence stating the choice and its reason.
## Step 2: Filter for ADR candidates
Apply this heuristic to determine which decisions warrant an ADR vs. which are incidental tips:
| Decision pattern | ADR candidate? |
|-----------------|----------------|
| "After X, always do Y" | Yes — process decision |
| "X depends on Y" | Yes — contract/coupling |
| "Use A instead of B because C" | Yes — architectural choice |
| "X is faster than Y" | Maybe — only if it changes approach |
| "Use --flag for better output" | No — tip, not decision |
Keep only entries that describe process changes, tooling contracts, or architectural choices. Tips and incidental observations don't warrant ADRs because they don't reflect decisions that constrain future work — capturing them as ADRs would dilute the ADR corpus and create noise in architecture documentation.
## Step 3: Draft ADR skeletons (only if candidates found)
Get the next safe ADR number once, then increment for subsequent candidates. `adr-query.py` has no number command, so take the highest numbered file in `adr/` plus one:
```bash
last=$(ls adr/ 2>/dev/null | grep -oE '^[0-9]+' | sort -n | tail -1); [ -n "$last" ] && echo $(( 10#$last + 1 )) || echo manual
```
Run it once for the first candidate. For additional candidates, increment the number manually (e.g., if first returns 132, use 133 for the second) because the command reads files on disk and the first skeleton is not written yet.
If the command prints `manual` (`adr/` is missing or has no numbered files), use placeholder numbers and note that the user should assign them before merging.
Draft to `adr/{number}-{slug}.md`:
```markdown
# ADR-{number}: {Title from the decision}
**Status**: Proposed
**Date**: {today}
**Source**: Drafted during a session pause; review before accepting
## Context
{Context that forced the decision}
## Decision
{The choice made, and the reason}
## Validation Criteria
- [ ] {Criterion derived from the decision}
```
Write the file to disk so it is visible in the next session even if Phase 4 fails.
## Step 4: Pass ADR data to Phase 4
Construct a `drafted_adrs` list in memory for use during the WRITE phase:
- If candidates were found: list of `{"number": N, "path": "adr/N-slug.md", "title": "..."}` entries
- If no candidates found: empty list — skip silently, no empty sections in output files
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |