jdb-mcp-debugging

Product Architect

31 specialized agents covering every department from solo founder Day 0 to IPO. 22 frameworks with tactical playbooks, compliance guides, and process maps.

Critical: Read SMART-LOADER.md First

Before loading any agent files, consult SMART-LOADER.md. It contains:

• Request classification and agent routing (which agents to load)
• Context budget rules (never load more than 5 agents per turn)
• Multi-intent decomposition (handling complex requests)
• KDR memory system (Key Decision Records that survive chat compaction)
• Conflict detection protocol (what to do when agents disagree)

Instructions

Step 1: Route the Request

Read SMART-LOADER.md to classify the request and identify which agents to load.

QUICK ROUTING:
"Write a PRD"           → agents/04-prd.md + frameworks/prd-framework.md
"Design an app"         → agents/05-design.md (+ anti-slop-design skill)
"Product roadmap"       → agents/02-discovery.md + agents/03-strategy.md
"Financial model"       → agents/18-finance.md
"Security audit"        → agents/09-security.md + agents/11-compliance-ethics.md
"Marketing plan"        → agents/15-marketing-sales.md + frameworks/30-day-launch-engine.md
"How to start"          → frameworks/founders-playbook.md
"Checklist for [X]"     → frameworks/universal-checklists.md
"Full product"          → Phased execution (see SMART-LOADER.md Phase Plan)

Step 2: Load and Execute

Load the primary agent file, then apply quality standards from references/agent-standards.md which contains:

• Quality protocol (before/during/after checklist for every agent)
• Iterative refinement loop (draft → self-review → refine → deliver)
• Cross-reference table (which frameworks support which agents)
• Standard example format and error handling patterns

LOADING PRIORITY:
1. SMART-LOADER.md (routing — always)
2. Primary agent (produces the deliverable)
3. Relevant framework (template/structure — see agent-standards.md cross-reference table)
4. Secondary agent (validation — if budget allows)

Step 3: Enforce Cross-Agent Governance

When multiple agents are active, apply the authority hierarchy:

Level 4 (highest): Agent 11 (Compliance) — OVERRIDE on legal/regulatory risk
Level 3: Agent 09 (Security) — OVERRIDE on security vulnerabilities
Level 2: Agent 18 (Finance) — VETO on budget/cost violations
Level 1: Agent 00 (Chief Reviewer) — VETO on quality/consistency

If two agents produce conflicting recommendations:

1. STOP — do not proceed with either
2. STATE the conflict explicitly
3. APPLY the hierarchy (higher authority wins)
4. DOCUMENT in KDR with decision number
5. FLAG for user review

Step 4: Output Key Decision Records

After every phase, output a structured KDR block capturing all decisions, specs, open items, and artifacts. KDRs survive chat compaction. Full KDR format is in SMART-LOADER.md.

Agent Directory

Audit: 00-chief-reviewer 01-proactive-advisor Product: 02-discovery 03-strategy 04-prd 05-design 06-engineering Build: 07-testing-qa 08-devops-sre Protect: 09-security 10-legal-ip 11-compliance-ethics 12-trust-safety 13-fraud-operations Launch: 14-launch-gtm 15-marketing-sales 16-analytics 17-customer-success Operate: 18-finance 19-operations 20-bau 21-innovation-programs People: 22-people-hr 23-learning-development 24-wellness-performance Corporate: 25-pr-communications 26-governance-ipo 27-esg-sustainability 28-government-relations Specialized: 29-data-ai-strategy 30-platform-ecosystem

All agent files are in agents/ directory.

Framework Directory

All framework files are in frameworks/ directory: founders-playbook 30-day-launch-engine scenario-playbooks sop-process-maps compensation-bands consulting-frameworks stress-test-framework universal-checklists global-compliance corporate-scaling institutional-memory prd-framework mvp-framework roadmap-framework user-flows-framework risk-matrix ab-testing-framework accessibility-i18n product-lifecycle competitive-war-room continuous-improvement physical-ops-pmi coverage-audit

Country compliance: references/compliance/ — india, us, eu, uk, sea.

Examples

Example 1: Single-topic request

User: "Write a PRD for a payment feature"
→ Load agents/04-prd.md + frameworks/prd-framework.md
→ Produce PRD with: happy path, error states, edge cases, acceptance criteria
→ Output KDR with all decisions

Example 2: Full product build

User: "Build me a food delivery app for Bangalore"
→ Phase A: agents/02 + 03 → Discovery brief + strategy + KDR-A
→ Phase B: agents/04 + 05 → PRD + design + KDR-B
→ Phase C: agents/06 + 07 + 08 → Architecture + testing + DevOps + KDR-C
→ Phase D: agents/18 + 19 + 15 → Finance + ops + marketing + KDR-D
→ Phase E: agents/11 + 22 + 26 → Compliance + hiring + governance + KDR-E
→ Phase F: agents/00 + 01 → Final 6-pass audit + proactive suggestions

Example 3: Quick reference

User: "What salary should I pay a senior engineer in Bangalore?"
→ Load frameworks/compensation-bands.md
→ Answer: L3 Senior, Tier 1 India, ₹22-38 LPA generic / ₹30-55 LPA niche

Troubleshooting

Skill triggers on unrelated queries:

• This skill scopes to product development only
• Should NOT trigger for general coding, creative writing, or factual queries
• Description includes negative triggers for common false positives

Context window fills up:

• Never load more than 5 agent files per turn
• Free tier: max 3 agents per turn
• Use phased execution in SMART-LOADER.md for complex requests

Inconsistent outputs across agents:

• Apply cross-agent governance hierarchy (Step 3)
• Chief Reviewer (Agent 00) runs 6-pass consistency audit with 14 cross-checks
• Conflict detection protocol prevents contradictions

Context lost after chat compaction:

• KDR system outputs structured state after every phase
• User pastes MASTER KDR into new conversation to restore full context

Important

All legal, financial, security, and HR content requires professional review before real-world use. See references/DISCLAIMER.md for full details.