Adapt a working follow-up report

For your first developer change, adapt Pipeline follow-up to your team's timing. The bundled report finds open opportunities with an overdue next action or at least seven quiet days. You will change that second rule to three days and verify which opportunities appear.

This exercise uses the real report source and its existing sandbox with fixed fictional records. It needs no database, model or sending account.

Start the source

You need Git, Node.js 22.16 or later, npm and an editor. For a local experiment, start from published main:

git clone https://github.com/JohnConnorCode/accelerate-site.git
cd accelerate-site
npm ci
npm run dev

Open the printed address and visit /demo/command-center. Explore the customer lifecycle, then stop your own server with Control-C. Read docs/NORTHSTAR.md and AGENTS.md before changing source. Assigned work uses the exact base and checkout from its execution packet.

Verify the original rule

From the repository, run:

npm run example:followup -- --days 7

The fixed example shows the seven-day opportunity and an overdue callback. A recent inquiry and a won job stay out. The command evaluates plugins/pipeline-watch/report.js, the report your extension actually supplies.

Change the useful rule

Open plugins/pipeline-watch/report.js. Find:

const stale = Number.isFinite(updated) && now - updated >= 7 * 86400000;

Change 7 to 3. The multiplier converts days to milliseconds; leave the overdue next-action and closed-stage rules in place.

Then verify the new result and refresh generated registration:

npm run example:followup -- --days 3
npm run build:extensions
npm run verify:extensions
npm run test:report-plugins
git diff --check

The three-day and four-day opportunities now appear alongside the seven-day opportunity and overdue callback. The check fails if the saved report still uses the old threshold. The existing report suite checks source boundaries, disabled execution and isolated evaluation.

Explain the result to a business user

The office now sees quiet opportunities sooner and can choose an appropriate next action. The report remains read-only: it identifies work worth inspecting and does not send a message or create a task.

Update the seven-day description in the Pipeline follow-up guide and its plugin README for your customized installation. Review your diff and run the repository's required checks before handing off application changes.

Use it with connected records

Follow installation, then enable Pipeline follow-up in Apps for your test workspace. Run the report, inspect its findings and open their source records. The fixture proves the rule over controlled input; a connected run also needs readable source registration and workspace access.

Keep building

Extension design helps you choose a module, report, workflow, provider adapter or AI tool. App design explains a dedicated business workspace. Give a coding agent a business brief with the useful result and acceptance example.

For shared backlog work, explicitly ask the agent to "pick up work from the backlog." The internal agent:go runner resolves the approved scope and worker checkout. Continue there through implementation, verification, commit and evidence submission for review. Use that claim workflow only for backlog pickup, preserve unfinished source, and record review, merge and deployment separately.