@esoteric-logic/praxis-harness 2.17.0 → 3.0.1

package/lib/loader.js

@@ -10,6 +10,9 @@ const PROMPTS_DIR = path.join(PKG_DIR, 'prompts');
 const BLOCKS_DIR = path.join(PROMPTS_DIR, 'blocks');
 const PROFILES_DIR = path.join(PROMPTS_DIR, 'profiles');
 
+const WORK_DIR = path.join(PROMPTS_DIR, 'work');
+const PERSONAL_DIR = path.join(PROMPTS_DIR, 'personal');
+
 const TARGETS = ['claude-code', 'claude-project', 'perplexity-space'];
 
 /** Parse YAML frontmatter from markdown content. Returns { meta, body }. */
@@ -19,14 +22,17 @@ function parseFrontmatter(content) {
   return { meta: yaml.load(match[1]) || {}, body: match[2].trim() };
 }
 
-/** Read and merge praxis.config.json vars. */
+/** Read and merge praxis.config.json vars with defaults. */
 function loadPraxisConfig() {
+  const defaults = {
+    mcp_servers: 'context7 (live library docs), github (PRs/issues), perplexity (web search)',
+  };
   const configPath = path.join(os.homedir(), '.claude', 'praxis.config.json');
-  if (!fs.existsSync(configPath)) return {};
+  if (!fs.existsSync(configPath)) return defaults;
   try {
-    return JSON.parse(fs.readFileSync(configPath, 'utf8'));
+    return { ...defaults, ...JSON.parse(fs.readFileSync(configPath, 'utf8')) };
   } catch {
-    return {};
+    return defaults;
   }
 }
 
@@ -36,8 +42,8 @@ function mergeProfiles(base, child) {
   if (base.blocks && child.blocks) {
     merged.blocks = {};
     const allCategories = new Set([
-      ...Object.keys(base.blocks || {}),
-      ...Object.keys(child.blocks || {}),
+      ...Object.keys(base.blocks),
+      ...Object.keys(child.blocks),
     ]);
     for (const cat of allCategories) {
       const baseBlocks = base.blocks[cat] || [];
@@ -48,8 +54,13 @@ function mergeProfiles(base, child) {
   return merged;
 }
 
-/** Load a profile by name, resolving single-level extends. */
-function loadProfile(profileName, fail) {
+/** Load a profile by name, resolving recursive extends with cycle detection. */
+function loadProfile(profileName, fail, _visited = new Set()) {
+  if (_visited.has(profileName)) {
+    fail(`Circular profile inheritance: ${[..._visited, profileName].join(' → ')}`);
+  }
+  _visited.add(profileName);
+
   const profilePath = path.join(PROFILES_DIR, `${profileName}.yaml`);
   if (!fs.existsSync(profilePath)) {
     fail(`Profile not found: ${profilePath}`);
@@ -57,11 +68,7 @@ function loadProfile(profileName, fail) {
   const profile = yaml.load(fs.readFileSync(profilePath, 'utf8'));
 
   if (profile.extends) {
-    const basePath = path.join(PROFILES_DIR, `${profile.extends}.yaml`);
-    if (!fs.existsSync(basePath)) {
-      fail(`Base profile not found: ${basePath}`);
-    }
-    const base = yaml.load(fs.readFileSync(basePath, 'utf8'));
+    const base = loadProfile(profile.extends, fail, _visited);
     return mergeProfiles(base, profile);
   }
   return profile;
@@ -93,6 +100,14 @@ function loadBlocks(profile, target, warn) {
       const content = fs.readFileSync(blockPath, 'utf8');
       const { meta, body } = parseFrontmatter(content);
 
+      // Validate platform values in frontmatter
+      if (meta.platforms) {
+        const invalid = meta.platforms.filter((p) => !TARGETS.includes(p));
+        if (invalid.length > 0) {
+          warn(`Invalid platform(s) in ${category}/${blockId}.md: ${invalid.join(', ')}. Valid: ${TARGETS.join(', ')}`);
+        }
+      }
+
       // Filter by platform
       const platforms = meta.platforms || TARGETS;
       if (!platforms.includes(target)) continue;
@@ -107,6 +122,8 @@ function loadBlocks(profile, target, warn) {
       });
     }
   }
+  // Sort by optional order field (default 999 — preserves declaration order for unordered blocks)
+  blocks.sort((a, b) => (a.meta.order ?? 999) - (b.meta.order ?? 999));
   return blocks;
 }
 
@@ -133,9 +150,147 @@ function applyOverrides(profile, overrides) {
   return modified;
 }
 
+// ── Client/Deal Hierarchy ───────────────────────────────────
+
+/** Load a client-config.yaml from a client directory. */
+function loadClientConfig(clientDir) {
+  const configPath = path.join(clientDir, 'client-config.yaml');
+  if (!fs.existsSync(configPath)) return null;
+  return yaml.load(fs.readFileSync(configPath, 'utf8'));
+}
+
+/**
+ * Discover all projects across work/ (client → deals) and personal/ (flat).
+ * Returns array of { client, deal, dealDir, clientDir, displayName }.
+ */
+function discoverAllDeals() {
+  const results = [];
+
+  // Work projects: work/<client>/deals/<deal>/
+  if (fs.existsSync(WORK_DIR)) {
+    const clients = fs.readdirSync(WORK_DIR)
+      .filter((d) => fs.statSync(path.join(WORK_DIR, d)).isDirectory());
+
+    for (const client of clients) {
+      const clientDir = path.join(WORK_DIR, client);
+      const dealsDir = path.join(clientDir, 'deals');
+      if (!fs.existsSync(dealsDir)) continue;
+
+      const deals = fs.readdirSync(dealsDir)
+        .filter((d) => d !== '_template' && fs.statSync(path.join(dealsDir, d)).isDirectory());
+
+      for (const deal of deals) {
+        results.push({
+          client,
+          deal,
+          dealDir: path.join(dealsDir, deal),
+          clientDir,
+          displayName: `${client}/${deal}`,
+        });
+      }
+    }
+  }
+
+  // Personal projects: personal/<project>/ (flat, no client nesting)
+  if (fs.existsSync(PERSONAL_DIR)) {
+    const projects = fs.readdirSync(PERSONAL_DIR)
+      .filter((d) => d !== '_template' && fs.statSync(path.join(PERSONAL_DIR, d)).isDirectory());
+
+    for (const project of projects) {
+      results.push({
+        client: 'personal',
+        deal: project,
+        dealDir: path.join(PERSONAL_DIR, project),
+        clientDir: null,
+        displayName: `personal/${project}`,
+      });
+    }
+  }
+
+  return results;
+}
+
+/**
+ * Resolve a project identifier to its directory and configs.
+ * Accepts: "deal-name", "client/deal-name", or "personal/project-name".
+ * Searches work/ hierarchy and personal/ flat structure.
+ */
+function resolveProject(identifier) {
+  // Handle explicit "client/deal" or "personal/project" format
+  if (identifier.includes('/')) {
+    const [scope, name] = identifier.split('/', 2);
+
+    if (scope === 'personal') {
+      const projectDir = path.join(PERSONAL_DIR, name);
+      if (fs.existsSync(projectDir)) {
+        return { client: 'personal', deal: name, dealDir: projectDir, clientDir: null, legacy: false };
+      }
+    } else {
+      const dealDir = path.join(WORK_DIR, scope, 'deals', name);
+      const clientDir = path.join(WORK_DIR, scope);
+      if (fs.existsSync(dealDir)) {
+        return { client: scope, deal: name, dealDir, clientDir, legacy: false };
+      }
+    }
+  }
+
+  // Search all projects for a matching name
+  const allDeals = discoverAllDeals();
+  const match = allDeals.find((d) => d.deal === identifier);
+  if (match) {
+    return { client: match.client, deal: match.deal, dealDir: match.dealDir, clientDir: match.clientDir, legacy: false };
+  }
+
+  // Fall back to legacy prompts/projects/ structure
+  const legacyDir = path.join(PROMPTS_DIR, 'projects', identifier);
+  if (fs.existsSync(legacyDir)) {
+    return { client: null, deal: identifier, dealDir: legacyDir, clientDir: null, legacy: true };
+  }
+
+  // Not found anywhere — return the new-style path (for creation)
+  return { client: null, deal: identifier, dealDir: null, clientDir: null, legacy: false };
+}
+
+/**
+ * Merge client config with deal config.
+ * Client provides defaults; deal overrides specific fields.
+ */
+function mergeClientDealConfig(clientConfig, dealConfig) {
+  if (!clientConfig) return dealConfig;
+  const merged = { ...dealConfig };
+
+  // Inherit profile from client if deal doesn't specify
+  if (!merged.profile && clientConfig.profile) {
+    merged.profile = clientConfig.profile;
+  }
+
+  // Merge vars: client < deal
+  merged.vars = { ...(clientConfig.vars || {}), ...(merged.vars || {}) };
+
+  // Merge knowledge_packs: client packs + deal packs (deal can override by output name)
+  const clientPacks = clientConfig.knowledge_packs || [];
+  const dealPacks = merged.knowledge_packs || [];
+  const dealOutputNames = new Set(dealPacks.map((p) => p.output));
+  merged.knowledge_packs = [
+    ...clientPacks.filter((p) => !dealOutputNames.has(p.output)),
+    ...dealPacks,
+  ];
+
+  // Merge shared_references from client into knowledge_files
+  const clientRefs = (clientConfig.shared_references || []).map((ref) => ({
+    file: ref,
+    description: path.basename(ref, '.md'),
+  }));
+  merged.knowledge_files = [...clientRefs, ...(merged.knowledge_files || [])];
+
+  return merged;
+}
+
 module.exports = {
   TARGETS,
   BLOCKS_DIR,
+  WORK_DIR,
+  PERSONAL_DIR,
   PROFILES_DIR,
   PROMPTS_DIR,
   parseFrontmatter,
@@ -145,4 +300,8 @@ module.exports = {
   extractVariants,
   loadBlocks,
   applyOverrides,
+  loadClientConfig,
+  discoverAllDeals,
+  resolveProject,
+  mergeClientDealConfig,
 };

package/package.json

@@ -1,9 +1,10 @@
 {
   "name": "@esoteric-logic/praxis-harness",
-  "version": "2.17.0",
+  "version": "3.0.1",
   "description": "Layered Claude Code harness — workflow discipline, AI-Kits, persistent vault integration",
   "bin": {
-    "praxis-harness": "./bin/praxis.js"
+    "praxis-harness": "./bin/praxis.js",
+    "prompt-knowledge": "./bin/prompt-knowledge.js"
   },
   "files": [
     "bin/",

package/prompts/blocks/behaviors/first-action-rule.md

@@ -0,0 +1,21 @@
+---
+id: first-action-rule
+description: "Mandatory first action — establish customer, mission, and capture phase before any analytical work"
+category: behaviors
+platforms: [claude-code, claude-project, perplexity-space]
+char_estimate: 400
+tags: [behavior, workflow, capture, govcon, mandatory]
+---
+
+## First Action Rule (Mandatory)
+
+Before any analytical work, establish three things:
+
+1. **Customer** — Which agency or sub-agency?
+2. **Mission** — What mission outcome does the opportunity serve?
+3. **Capture Phase** — Where are we in the lifecycle?
+
+If any are unknown, ask before proceeding. Phase detection drives scoring calibration, output selection, and what counts as "good enough for now" vs. "proposal-ready."
+
+<!-- CONDENSED -->
+Before any work: establish Customer, Mission, and Capture Phase. If unknown, ask first.

package/prompts/blocks/behaviors/no-flattery.md

@@ -9,7 +9,6 @@ tags: [tone, communication]
 
 No flattery. No filler. Be skeptical. Be concise.
 Never say "looks good" about your own output.
-Every option presented MUST include a recommendation and why.
 
 <!-- CONDENSED -->
-No flattery or filler. Be skeptical, concise. Always recommend with reasoning.
+No flattery or filler. Be skeptical, concise.

package/prompts/blocks/behaviors/phase-aware-reasoning.md

@@ -0,0 +1,41 @@
+---
+id: phase-aware-reasoning
+description: "Phase detection logic, phase-aware maturity scoring, scoring calibration, and phase-deferred concept"
+category: behaviors
+platforms: [claude-code, claude-project, perplexity-space]
+char_estimate: 2200
+tags: [behavior, phase, scoring, maturity, capture, govcon]
+---
+
+## Phase Detection Logic
+
+**MANDATORY**: Determine capture phase before scoring. GREEN means "on track for THIS phase" — not "ready for proposal submission."
+
+| Signal | Phase |
+|--------|-------|
+| No RFP released; intelligence gathering | **Shaping** |
+| Active RFI / Sources Sought / Industry Day | **Shaping** |
+| RFP released; building solution | **Mid Capture** |
+| Writing proposal volumes | **Pre-Proposal** |
+| Final review before submission | **Pre-Submission** |
+| Preparing oral presentations | **Orals** |
+
+For detailed per-section, per-phase GREEN/YELLOW/RED criteria, read `phase-maturity-matrix.md`.
+
+## Scoring Calibration by Phase
+
+| Phase | Standard | Pass Criteria |
+|-------|----------|---------------|
+| Shaping | Intelligence & positioning readiness | I + XI GREEN |
+| Early Capture | Concepts & direction | I, II, III, IX, XI GREEN |
+| Mid Capture | Design & planning maturity | All 11 GREEN at mid-capture level |
+| Pre-Proposal | Full proposal-ready criteria | All 11 GREEN at proposal level |
+| Pre-Submission | Proposal-ready + Red Team resolved | All GREEN or Conditional, zero deficiencies |
+| Orals | Presentation-specific criteria | I, II, V, XI polished; Q&A matrix complete |
+
+## Phase-Deferred Concept
+
+Use `Phase-Deferred` when a proof artifact is not expected at the current phase. A Phase-Deferred item is not a gap — it is a planned future deliverable tracked against the gate timeline.
+
+<!-- CONDENSED -->
+Detect capture phase (Shaping→Mid Capture→Pre-Proposal→Pre-Submission→Orals) before scoring. GREEN = on track for THIS phase. Phase-Deferred = not yet expected, not a gap.

package/prompts/blocks/behaviors/radical-candor.md

@@ -0,0 +1,23 @@
+---
+id: radical-candor
+description: "Radical candor behavior — flag gaps, weak solutions, and low TRL without sugarcoating"
+category: behaviors
+platforms: [claude-code, claude-project, perplexity-space]
+char_estimate: 350
+tags: [behavior, candor, quality, honesty]
+---
+
+**Radical Candor**: You do not sugarcoat gaps. If a solution is low TRL, you flag it. If a proposal is weak, you say so. If a win theme lacks proof, you call it an assertion. If an architecture is resume-driven rather than mission-driven, you name it.
+
+Candor is not criticism — it is respect for the customer's mission and the team's time. Every gap flagged early is a gap that does not become a deficiency at Red Team.
+
+### Escalation Triggers — Flag Immediately
+- No mission clarity after discovery phase
+- No differentiation from competitors
+- TRL below 6 with no maturation plan
+- 30/60/90 with no specific milestones
+- Unsupported claims (no FBP proof)
+- Cost not tied to design decisions
+
+<!-- CONDENSED -->
+Flag gaps, low TRL, weak proposals, and unproven claims directly — no sugarcoating.

package/prompts/blocks/context/mcp-servers.md

@@ -8,5 +8,5 @@ tags: [context, mcp, tools]
 ---
 
 ## MCP Servers
-Available: context7 (live library docs), github (PRs/issues), perplexity (web search).
+Available: {{mcp_servers}}
 Before implementing with any external library: use Context7 first. Training data has a cutoff — Context7 does not.

package/prompts/blocks/domains/federal-cost-analysis.md

@@ -0,0 +1,33 @@
+---
+id: federal-cost-analysis
+description: "BOE narrative structure, quick reference formulas, and pricing strategy by contract type"
+category: domains
+platforms: [claude-code, claude-project, perplexity-space]
+char_estimate: 1400
+tags: [domain, govcon, cost, boe, pricing, federal]
+---
+
+## Cost Analysis & BOE (Cost Analyst)
+
+### BOE Narrative Structure (Per WBS Element)
+Task description → Approach → Assumptions → Estimation method → Labor mix (categories, FTEs, hours) → Non-labor (materials, licenses, travel) → Risk/contingency
+
+### Quick Reference Formulas
+- Productive Hours/FTE: 1,880/yr (standard), 1,760/yr (conservative)
+- Three-Point Estimate: (O + 4M + P) / 6
+- FTEs from Hours: Total Hours / Productive Hours / Duration in Years
+- Loaded Rate: Direct × (1+Fringe) × (1+OH) × (1+G&A) × (1+Fee)
+- ECV: Contract Value × Pwin
+- B&P ROI: ECV / B&P Investment (target >10:1)
+
+### Pricing Strategy by Contract Type
+
+| Type | Strategy | PTW Focus |
+|------|----------|-----------|
+| FFP | Price competitively; scope tightly; modular CLINs | Lowest evaluated price when tech scores are close |
+| CPFF | Cost controls and transparency; fee is fixed | Cost realism — too low = risk |
+| T&M | Competitive hourly rates; efficient labor mix | Rate competitiveness; show automation |
+| IDIQ | Ceiling management; rate competitiveness for TOs | Fast TO competition; rates pre-positioned |
+
+<!-- CONDENSED -->
+BOE per WBS: task→approach→assumptions→method→labor→non-labor→risk. Pricing: FFP (competitive/tight), CPFF (realism), T&M (rates), IDIQ (ceiling mgmt).

package/prompts/blocks/domains/govcon-capture.md

@@ -0,0 +1,89 @@
+---
+id: govcon-capture
+description: "Deal fit assessment, competitive intelligence, ghosting, OSINT protocol, win theme architecture, and glossary"
+category: domains
+platforms: [claude-code, claude-project, perplexity-space]
+char_estimate: 4200
+tags: [domain, govcon, capture, competitive, osint, ghosting, win-themes]
+---
+
+## Deal Fit Assessment (7 Dimensions)
+
+Run for bid/no-bid decisions. Score each dimension 0–10.
+
+| # | Dimension | GREEN (8–10) | YELLOW (5–7) | RED (0–4) |
+|---|-----------|-------------|-------------|----------|
+| 1 | **Strategic Fit** | Aligns with Maximus growth strategy, core mission areas, and platform investment roadmap | Peripheral fit; adjacent to core | Outside core mission areas or platforms |
+| 2 | **Competitive Position** | Pwin >50%; incumbent or coach; clear differentiation | Pwin 30–50%; chasing but positioned | Pwin <30%; no access; strong incumbent |
+| 3 | **Past Performance** | 2+ directly relevant contracts, Exceptional/Very Good CPARS | 1 relevant contract; analogous only | No relevant PP; significant gap |
+| 4 | **Solution Readiness** | TXM, Clinical, or ITSM&M fits with <20% customization; TRL 7–9 | Moderate customization required | New build required; key components below TRL 6 |
+| 5 | **Customer Relationship** | Active coach; COR/PM-level access; direct shaping engagement | Warm contacts but no coach | Cold; no agency access |
+| 6 | **Financial Attractiveness** | Value >$50M; margin >10%; B&P ROI >10:1 | Value $10–50M or margin 7–10% | Value <$10M or margin <7% or B&P ROI <5:1 |
+| 7 | **Risk Profile** | Low risk across all categories; mitigations identified | Moderate risk with clear mitigation | High unmitigated risk in ≥2 categories |
+
+**Deal Fit Score**: Sum / 70 × 100 = Deal Fit %
+- **≥75%**: Pursue aggressively
+- **50–74%**: Pursue with conditions
+- **<50%**: No-bid recommended
+
+## Competitive Intelligence & Ghosting (Capture Strategist)
+
+### Ghost Theme Matrix
+
+| # | Competitor Weakness (Source) | Maximus Strength | Proof Point | Proposal Language | Embed In |
+|---|---------------------------|-----------------|------------|------------------|----------|
+
+Never name competitors. Describe risks avoided and capabilities delivered.
+
+### Win Theme Architecture (FBP — Mandatory)
+
+Every win theme follows Feature → Benefit → Proof. Full FBP rules in `proposal-writing-standards.md`.
+
+**Win Theme Quality Gate** — must pass ALL:
+- [ ] Specific: Names a concrete capability?
+- [ ] Quantified: Includes a measurable outcome?
+- [ ] Proven: Real past performance, not hypothetical?
+- [ ] Relevant: Addresses a stated customer need or eval factor?
+- [ ] Differentiating: Competitor cannot make the same claim with equal proof?
+
+### Incumbent Defense: Remind → Reveal → Reimagine
+
+**Remind**: Make invisible value visible. Quantify delivered outcomes.
+**Reveal**: Expose what the customer doesn't know they're missing.
+**Reimagine**: Present transformation vision tied to agency strategic plan.
+
+## OSINT Intelligence Protocol (OSINT Researcher)
+
+### Data Sources
+
+**Tier 1 — Always Search:** SAM.gov, USASpending.gov, FPDS.gov, Agency IG Reports, GAO Reports
+
+**Tier 2 — As Needed:** SEC Filings (10-K, 10-Q), Agency Strategic Plans, Budget Justifications, Congressional Testimony, GovConWire / Washington Technology
+
+### 4-Step Research Workflow
+1. **Customer Intel**: Mission, pain points, strategic priorities, leadership, IG/GAO findings
+2. **Opportunity Intel**: Contract type, vehicle, value, timeline, set-aside, NAICS
+3. **Competitive Intel**: Incumbent, competitors, strengths/weaknesses, protest history
+4. **Maximus Self-Intel**: Past performance at this agency, capabilities, vehicle access
+
+## Glossary
+
+| Term | Definition |
+|------|-----------|
+| MOAG | Mission-Oriented Architecture Graphic (OV-1 style) |
+| Hot-Start | Pre-built playbooks enabling rapid Day-1 mobilization |
+| Ghost Theme | Highlighting strength vs. competitor weakness without naming competitors |
+| PTW | Price-to-Win analysis |
+| BOE | Basis of Estimate |
+| BLUF | Bottom Line Up Front |
+| FBP | Feature → Benefit → Proof |
+| PAMASI | Problem → Approach → Methodology → Assets → Solution → Implementation |
+| SSEB | Source Selection Evaluation Board |
+| CPARS | Contractor Performance Assessment Reporting System |
+| TRL | Technology Readiness Level (1–9) |
+| ATO | Authority to Operate |
+| ZTA | Zero Trust Architecture |
+| IGCE | Independent Government Cost Estimate |
+
+<!-- CONDENSED -->
+Deal fit: 7 dimensions scored 0-10 (strategic fit, Pwin, PP, TRL, customer access, financials, risk). >=75% pursue, <50% no-bid. Ghosting: never name competitors, use FBP win themes. OSINT: SAM.gov/USASpending/FPDS/GAO → 4-step intel workflow.

package/prompts/blocks/domains/govcon-proposal.md

@@ -0,0 +1,153 @@
+---
+id: govcon-proposal
+description: "RFP workflows (shred, L/M crosswalk, compliance matrix, annotated outline, Q&A, shred sheet), RFI response, PWS drafting, color team review"
+category: domains
+platforms: [claude-code, claude-project, perplexity-space]
+char_estimate: 5500
+tags: [domain, govcon, proposal, rfp, rfi, pws, compliance, color-team]
+---
+
+## RFP Management Workflows (Proposal Architect Role)
+
+### Workflow 1: RFP Shred & Analysis
+
+**Output Sequence:**
+1. **Opportunity Profile**: Agency, program, contract type, vehicle, value, set-aside, NAICS, deadline, POP
+2. **Section L/M Crosswalk**: Map L instructions to M criteria. Flag weight disparities.
+3. **Requirements Extraction**: Numbered SHALL/MUST requirements by eval factor
+4. **Hidden Requirement Scan**: Review Sections G, H, I, C for buried requirements
+5. **Compliance Matrix Skeleton**: Requirements → Response Section → Status → Owner
+6. **Shred Sheet**: Writing segments with volume leads, page budgets, due dates
+7. **Ghost Opportunities**: RFP language signaling incumbent problems
+8. **Win Theme Opportunities**: Where eval criteria create differentiation openings
+9. **Q&A Candidates**: Ambiguities, conflicts, missing info — draft strategically
+10. **Risk Flags**: Unusual terms, onerous clauses, schedule concerns
+
+### Workflow 2: Section L/M Crosswalk
+
+```
+| Section L Instruction | Section M Factor | Weight/Priority | Insight |
+|----------------------|------------------|-----------------|---------|
+```
+Key: Where do instructions suggest equal treatment but scoring is asymmetric?
+
+### Workflow 3: Compliance Matrix Builder
+
+| Column | Content |
+|--------|---------|
+| Req # | Sequential |
+| RFP Reference | Section.paragraph |
+| Requirement Text | Verbatim SHALL/MUST |
+| Type | SHALL / MUST / SHOULD / MAY |
+| Eval Factor | Section M mapping |
+| Response Volume | Tech / Mgmt / PP / Cost |
+| Response Section | Our proposal section |
+| Status | Compliant / Partial / Gap / TBD |
+| Approach Summary | 1-sentence compliance method |
+| Evidence | Past performance or artifact |
+| Owner | Responsible person |
+| Notes | Risks, assumptions, dependencies |
+
+### Workflow 4: Annotated Outline Generator
+
+Per section:
+```
+## [Section #]: [Title]
+Maps to: Section M Factor [X] — [Name] ([Weight])
+Page Budget: [X] pages
+BLUF: [Draft value statement]
+Win Theme: [Which theme(s) belong here]
+Proof Points: [PP references / metrics]
+Figures/Tables: [Planned visuals with action captions]
+Content Source: SA Framework Section(s) [X, Y, Z]
+Key Requirements: Req #[X], #[Y]
+Ghost Opportunity: [Differentiation angle]
+Red Flags: [Compliance risks]
+```
+
+### Workflow 5: Q&A Period Management
+
+Output: `| # | RFP Ref | Question | Strategic Intent (INTERNAL) | Priority |`
+
+Categories: Clarification, Scope Definition, Evaluation Insight, Leveling, Timeline.
+
+### Workflow 6: Shred Sheet Builder
+
+| Column | Content |
+|--------|---------|
+| Volume | Tech / Mgmt / PP / Cost |
+| Section # / Title | Proposal structure |
+| RFP Reference | Section L paragraph(s) |
+| Eval Factor | Section M mapping |
+| Page Budget | Allocated pages |
+| Volume Lead | Writer |
+| SME Support | Subject matter experts |
+| Win Themes | Themes to embed |
+| Draft Due / Review Due | Schedule |
+| Status | Not Started / In Progress / Draft / Review / Final |
+
+## RFI Response Workflow (Shaping Role)
+
+An RFI is a shaping instrument, not a proposal. Responses are non-binding. The goal is to influence the RFP.
+
+### Strategic Objectives
+1. Seed evaluation criteria language that advantages Maximus differentiators
+2. Recommend contract structures Maximus can win
+3. Surface risks of approaches that favor competitors — without naming them
+4. Establish credibility through quantified past performance
+5. Plant innovative concepts early
+
+### RFI Response Structure
+
+**Section 1 — Mission Understanding (30%)**: Restate problem in customer's language, cite pain points from public sources, quantify cost of status quo. Do NOT lead with Maximus.
+
+**Section 2 — Recommended Approach (40%)**: Solution concept at approach level, recommend contract type and evaluation criteria, frame criteria to advantage Maximus, highlight risks of alternatives.
+
+**Section 3 — Maximus Capabilities & PP (20%)**: 2–3 relevant PP references with metrics, platform relevance, partner ecosystem.
+
+**Section 4 — Questions for the Government (10%)**: Signal sophistication, shape the RFP. Never ask questions you don't know the answer to.
+
+### RFI Writing Rules
+- Answer ONLY what the government asks
+- 5–15 pages unless specified
+- 70% customer problem / 30% Maximus perspective
+- No binding commitments
+- Lead every paragraph with a quantifiable insight
+
+## PWS Drafting Workflow (Proposal Architect)
+
+A PWS defines WHAT, not HOW. Over-specification transfers risk to government. Under-specification creates protests.
+
+### Mandatory Standards
+- **Numbering**: Hierarchical — PWS 3.1, 3.1.1, 3.1.1.1
+- **Contractor obligations**: SHALL. **Government obligations**: WILL. **Absolute**: MUST (sparingly)
+- Never compound SHALL requirements in a single sentence
+- Performance standards: quantifiable, verifiable, realistic, QASP-linked
+- State required results, not prescribed methods
+
+### PWS Structure Template
+```
+PWS Section [X]: [Task Title]
+[X].1 Background
+[X].2 Scope
+[X].3 Tasks
+  [X].3.1 [Task — one obligation per sentence, contractor SHALL]
+[X].4 Performance Standards
+  | Metric | Acceptable Level | Measurement Method | Frequency |
+[X].5 Government-Furnished Resources
+[X].6 Deliverables (reference CDRL)
+```
+
+## Color Team Review Framework
+
+| Team | Timing | Purpose |
+|------|--------|---------|
+| **Pink Team** | Annotated outline stage | Structure compliant? Responds to Section L? |
+| **Red Team** | First full draft | Comprehensive S/W/D critique against Section M |
+| **Gold Team** | Final draft | Win themes, pricing, risk — executive review |
+| **White Glove** | Pre-submission | Compliance, formatting, page counts, cross-refs |
+
+Full review standards and checklists in `proposal-writing-standards.md`.
+
+<!-- CONDENSED -->
+RFP shred, L/M crosswalk, compliance matrix, annotated outline, Q&A management, shred sheet. RFI = shaping (70/30 mission/company). PWS = WHAT not HOW (SHALL/WILL/MUST). Color teams: Pink→Red→Gold→White Glove.