Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/industrial-ai-research

industrial-ai-research

Verified

Industrial AI literature research with mandatory intake questions, venue-aware source prioritization, structured report outputs, and survey draft generation. Use when the user needs up-to-date research on predictive maintenance, intelligent scheduling, industrial anomaly detection, smart manufacturing, cyber-physical systems, edge AI for automation, or crossover robotics-for-industry topics. Also trigger for adjacent terms: "digital twin", "industrial IoT", "Industry 4.0", "manufacturing AI", "factory automation", "process optimization", or "survey draft" in industrial contexts.

references/modules/SURVEY_EVIDENCE.md

View on GitHub
# Module: Survey Evidence Pack Assembly (Phase S2)

Assemble structured evidence for every H3 subsection. This phase produces data artifacts only — no prose.

## Prerequisites

- Phase S1 complete: `outline.yml` approved by user, `taxonomy.md` finalized.
- Verified paper set available with full metadata.

## Evidence Pack Structure

For each H3 subsection in `outline.yml`, produce one evidence file at `{output-dir}/evidence/{section-slug}.md`:

```markdown
# Evidence Pack: [Section ID] — [Sub-branch Title]

## Claim Candidates

- **[Claim 1]**: [Paper ID] — "[verbatim or close-paraphrase snippet from abstract/conclusion]"
- **[Claim 2]**: [Paper ID] — "[snippet]"
- ...

## Comparison Table

| Paper | Method | Dataset | Key Metric | Result | Deployment Evidence |
|-------|--------|---------|------------|--------|---------------------|
| ... | ... | ... | ... | ... | None / Simulation / Pilot / Production |

## Anchor Facts

Quantitative facts that the writer must use:

- [Fact 1]: [Paper ID] — [exact number and context]
- [Fact 2]: [Paper ID] — [exact number and context]
- ...

## Gaps and Limitations

- **[Gap 1]**: evidence from [Paper IDs] — [brief description]
- **[Limitation 1]**: [Paper IDs] — [brief description]
- ...

## Allowed Citations

- **Primary** (this H3): [list of paper IDs]
- **Chapter-level** (parent H2): [list of paper IDs]
- **Global** (use sparingly): [list of paper IDs]

## Evidence Density Flag

- Status: SUFFICIENT | THIN_EVIDENCE
- If THIN_EVIDENCE: [explanation of what is missing]
```

## Key Rules

### No Prose

Evidence packs contain only structured data: bullet lists, tables, and tagged citations. The writer module (Phase S3) converts these into narrative text.

### No Fabrication

- Every claim candidate must trace to a specific snippet from a verified paper.
- Every anchor fact must include the exact quantitative value from the source.
- If a claim cannot be sourced, do not include it.

### Citation Scope Locking

The writer (Phase S3) is restricted to citations listed in the evidence pack:

- **Primary citations**: directly relevant to this H3. Use freely.
- **Chapter-level citations**: relevant to the parent H2 but not specific to this H3. Use for context.
- **Global citations**: foundational or cross-cutting papers. Use sparingly (max 2 per H3).

### Thin Evidence Handling

If a subsection has fewer claims or citations than the minimum required by the length tier, mark it as `THIN_EVIDENCE` and:

- Do NOT pad with filler claims or tangential papers.
- Flag explicitly so the writer can adjust depth expectations.
- Consider suggesting to the user that this subsection be merged with a sibling.

## Evidence Density Requirements

Minimum thresholds per H3 subsection, by length tier:

| Length Tier | Min claim candidates | Min unique citations | Min comparison table rows |
|-------------|---------------------|---------------------|--------------------------|
| Short | 3 | 5 | 3 |
| Standard | 5 | 8 | 5 |
| Comprehensive | 8 | 12 | 8 |

## Citation Map

After all evidence packs are assembled, produce `{output-dir}/citation-map.md`:

```markdown
# Citation Map

## Section-to-Citation Binding

| Section ID | Section Title | Primary Citations | Chapter Citations | Global Citations |
|-----------|--------------|-------------------|-------------------|------------------|
| S3.1 | [title] | [IDs] | [IDs] | [IDs] |
| S3.2 | [title] | [IDs] | [IDs] | [IDs] |
| ... | ... | ... | ... | ... |

## Citation Frequency

| Paper ID | First Author | Year | Sections Referenced | Role |
|----------|-------------|------|--------------------|----- |
| ... | ... | ... | [list] | Primary / Chapter / Global |
```

## Artifacts Produced

| Artifact | Format | Location |
|----------|--------|----------|
| `evidence/{section-slug}.md` | Markdown per H3 | `{output-dir}/evidence/` |
| `citation-map.md` | Markdown table | `{output-dir}/citation-map.md` |
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall