Fresh prompts for all agents (18 Oct 2026)¶
Paste one block per agent, once, in an attended chat. Each points to the repository; nothing needs relaying later. After this, your standard verbs (PROCEED, CONTINUE, STATUS, HOLD, REDUCE) are enough.
Common part (already inside each block below)¶
New process from today. Read, in this order: 1. Rules (all sections; new: §13 durable notes, §14 heartbeat and nobody waits, §15 quality bar): https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/mmdep-agent-rules.md 2. Heartbeat at the start of every run: https://github.com/moneymarche-dev/MMDEP/blob/control/HEARTBEAT.md 3. Your rows in the answers relay: https://github.com/moneymarche-dev/MMDEP/blob/main/docs/relay/answers.md 4. Sprint plan v3 (your stories and order): https://github.com/moneymarche-dev/MMDEP/blob/main/docs/plans/sprints-2026-10-18.md 5. Label vocabulary and routing block for new issues: https://github.com/moneymarche-dev/MMDEP/blob/main/docs/registers/labels.md and DR-008 §3 https://github.com/moneymarche-dev/MMDEP/blob/main/docs/decisions/DR-008-routing-preflight-segregation.md Always queue laptop work as issues and never wait; take your recommended option on reversible questions and mark it ASSUMED; ask Atul only about production, scope, money, compliance or irreversible steps. Scheduled runs only read: put your complete result in the run output; attended runs and Run-now commit it. Update your owner notes with anything Atul tells you.
API / MM-Cron (account A)¶
PROCEED — fresh start, 18 Oct. Sprint 1 has started: plan it in exactly three PROCEEDs (rules §16 and §16a: this PROCEED = all designs; next = all issues; third = preflight of every issue). After that, finish each epic in at most three PROCEEDs; start every reply with a counter such as 'Epic: X — PROCEED 1 of 3' and end with what the next PROCEED does. No questions mid-epic except rules §14 cases. Questions route by rules §14a: business only to Atul (question-atul); technical to the owning agent (ask-<project>) or MMDEP-PM (ask-mmdep). Read: rules https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/mmdep-agent-rules.md (§13–§15 new), heartbeat https://github.com/moneymarche-dev/MMDEP/blob/control/HEARTBEAT.md, your answers rows https://github.com/moneymarche-dev/MMDEP/blob/main/docs/relay/answers.md (17 Oct: API and MM-Cron priorities, category roll-up, knowledge check on AMFI factsheet links, ULIP scope), sprint plan https://github.com/moneymarche-dev/MMDEP/blob/main/docs/plans/sprints-2026-10-18.md.
API order: (1) duplicate and missing NAV records; (2) inventory of every direct database reader, towards APIs only; (3) column documentation / OpenAPI (search for the earlier swagger work first), catalogue APIs first (owned by MCRM), then MF APIs; (4) stgapi up. MM-Cron order: (1) logs and no direct database writes; (2) AMC fund details (TER, fund size, inception date); (3) AMC performance and risk ratios; (4) portfolio composition.
First, answer the knowledge check (AMC list route and table; where AMFI factsheet links are documented) in your status. Release 1 (security batch) continues. New issues carry the routing block. Never wait; queue laptop work; ask Atul only per rules §14.
MWMC (account A)¶
PROCEED — fresh start, 18 Oct. Sprint 1 has started: plan it in exactly three PROCEEDs (rules §16 and §16a: this PROCEED = all designs; next = all issues; third = preflight of every issue). After that, finish each epic in at most three PROCEEDs; start every reply with a counter such as 'Epic: X — PROCEED 1 of 3' and end with what the next PROCEED does. No questions mid-epic except rules §14 cases. Questions route by rules §14a: business only to Atul (question-atul); technical to the owning agent (ask-<project>) or MMDEP-PM (ask-mmdep). Read: rules https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/mmdep-agent-rules.md (§13–§15 new), heartbeat https://github.com/moneymarche-dev/MMDEP/blob/control/HEARTBEAT.md, your answers rows https://github.com/moneymarche-dev/MMDEP/blob/main/docs/relay/answers.md (17 Oct: category status/show-in-menu and roll-up rule), sprint plan https://github.com/moneymarche-dev/MMDEP/blob/main/docs/plans/sprints-2026-10-18.md.
Sprint 1: SEO basics live (canonicals, titles, sitemaps, breadcrumb), route crawler on request plus daily route health; you are the pilot for the Test harness. In your next status, report where production reads the category status and show-in-menu flags and how it rolls hidden categories up one level (file, function, query).
Your open question #123 (unknown deep MF routes): take your recommended option, mark it ASSUMED, continue. New issues carry the routing block. Never wait; ask Atul only per rules §14.
MCRM (account A)¶
PROCEED — fresh start, 18 Oct. Sprint 1 has started: plan it in exactly three PROCEEDs (rules §16 and §16a: this PROCEED = all designs; next = all issues; third = preflight of every issue). After that, finish each epic in at most three PROCEEDs; start every reply with a counter such as 'Epic: X — PROCEED 1 of 3' and end with what the next PROCEED does. No questions mid-epic except rules §14 cases. Questions route by rules §14a: business only to Atul (question-atul); technical to the owning agent (ask-<project>) or MMDEP-PM (ask-mmdep). Read: rules https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/mmdep-agent-rules.md (§13–§15 new), heartbeat https://github.com/moneymarche-dev/MMDEP/blob/control/HEARTBEAT.md, your answers rows https://github.com/moneymarche-dev/MMDEP/blob/main/docs/relay/answers.md (17 Oct: catalogue API ownership, category roll-up rule, ULIP for ICICI Prudential Life as your next case, MCRM destination as the operations harness), sprint plan https://github.com/moneymarche-dev/MMDEP/blob/main/docs/plans/sprints-2026-10-18.md.
First: bring open PRs from 66 down to 5 (merge docs-only ones that are ready, close superseded ones, keep a list). Then the category tree including the roll-up rule. Then ICICI Prudential Life ULIP product + fund model (active and legacy funds), reusing the MF fund structures. Record the destination (operations harness) in your VISION document; don't build it now.
New issues carry the routing block. Never wait; ask Atul only per rules §14.
Portfolio Engine (PE)¶
PROCEED — fresh start, 18 Oct. Sprint 1 has started: plan it in exactly three PROCEEDs (rules §16 and §16a: this PROCEED = all designs; next = all issues; third = preflight of every issue). After that, finish each epic in at most three PROCEEDs; start every reply with a counter such as 'Epic: X — PROCEED 1 of 3' and end with what the next PROCEED does. No questions mid-epic except rules §14 cases. Questions route by rules §14a: business only to Atul (question-atul); technical to the owning agent (ask-<project>) or MMDEP-PM (ask-mmdep). Read: rules https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/mmdep-agent-rules.md (§13–§15 new), heartbeat https://github.com/moneymarche-dev/MMDEP/blob/control/HEARTBEAT.md, your answers rows https://github.com/moneymarche-dev/MMDEP/blob/main/docs/relay/answers.md (run-jobs #336 PASS, #337 done twice, identical report), sprint plan https://github.com/moneymarche-dev/MMDEP/blob/main/docs/plans/sprints-2026-10-18.md.
Sprint 1: client portfolio review workbook (#309) accepted after your review of the returned workbook; objective selection (#321) ready for Atul's merge decision. #329, #330 and #375 wait for Atul: meanwhile take reversible defaults where the rules allow and mark them ASSUMED. Run-jobs: keep the exact head and CI gate in the issue; MMDEP runs them at check-ins while the heartbeat is ACTIVE.
New issues carry the routing block. Never wait; ask Atul only per rules §14.
WPDev (account C)¶
PROCEED — fresh start, 18 Oct. Sprint 1 has started: plan it in exactly three PROCEEDs (rules §16 and §16a: this PROCEED = all designs; next = all issues; third = preflight of every issue). After that, finish each epic in at most three PROCEEDs; start every reply with a counter such as 'Epic: X — PROCEED 1 of 3' and end with what the next PROCEED does. No questions mid-epic except rules §14 cases. Questions route by rules §14a: business only to Atul (question-atul); technical to the owning agent (ask-<project>) or MMDEP-PM (ask-mmdep). Read: rules https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/mmdep-agent-rules.md (§13–§15 new), heartbeat https://github.com/moneymarche-dev/MMDEP/blob/control/HEARTBEAT.md, your answers rows https://github.com/moneymarche-dev/MMDEP/blob/main/docs/relay/answers.md (17 Oct: category status/show-in-menu and roll-up rule), sprint plan https://github.com/moneymarche-dev/MMDEP/blob/main/docs/plans/sprints-2026-10-18.md.
Your CI runs on the laptop runner: rebase !302 on main and rerun; keep open MRs at 5 or fewer. In your next status, report where the website reads category status/show-in-menu and how hidden categories roll up. You are now in the MMDEP way of working: owner notes, routing block on new issues, never wait, ask Atul only per rules §14.
MMDEP assistant (account A)¶
PROCEED — fresh start, 18 Oct. Use your saved prompt https://github.com/moneymarche-dev/MMDEP/blob/main/docs/agents/projects/mmdep-assistant-prompt-2026-10-16.md with three additions: (1) when an issue body has a HOLD or a newer authorization section, that wins over older comments; (2) also list the harness status from https://github.com/moneymarche-dev/MMDEP/blob/control/harness/LATEST.md ; (3) flag any agent asking Atul something rules §14 says it need not ask.