Menu
Wire generated artifacts together. Identifies integration points and produces actionable wiring checklist
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | manifold-m6-integrate |
| description | Wire generated artifacts together. Identifies integration points and produces actionable wiring checklist |
Wire generated artifacts together by identifying integration points and producing actionable checklists.
Discipline: This command follows
references/execution-discipline.md— the Iron Law of verification, the never-start-on-mainrule, and the Red Flags below.
/manifold:m6-integrate <feature-name> [--check-only] [--auto-wire]
Flags:
--check-only - Show integration checklist without making changes--auto-wire - Attempt automatic integration where safeWhen recording integration, maintain v3 schema structure:
{
"iterations": [
{
"number": 6,
"phase": "integrate",
"timestamp": "2026-04-04T00:00:00Z",
"result": "Identified 5 integration points, 3 auto-wireable, 2 manual",
"integration_points": 5,
"completed": 0,
"pending": 5,
"auto_wireable": 3,
"manual_required": 2
}
],
"convergence": {
"status": "IN_PROGRESS",
"criteria": {
"all_invariants_satisfied": true,
"all_required_truths_satisfied": false,
"no_blocking_gaps": true
}
}
}
See
SCHEMA_REFERENCE.mdfor valid convergence statuses, iteration fields, and integration checklist structure.
Problem observed: /manifold:m4-generate creates artifacts in isolation. Integration was manual and error-prone.
From graph-d-validation learnings:
These gaps emerged AFTER generation because wiring wasn't tracked.
/manifold:m6-integrate performs:
Uses static pattern matching (no code execution) to identify wiring needs:
| Artifact Type | Integration Pattern | Detection Method |
|---|---|---|
| Rust modules | mod declarations | Grep for pub mod |
| Feature flags | Cargo.toml features | Grep for [features] |
| TypeScript modules | Import/export | Grep for export, import |
| Config files | Reference to new configs | Grep for config paths |
| Tests | Test imports | Grep for test utilities |
/manifold:m6-integrate graph-d-validation
INTEGRATION ANALYSIS: graph-d-validation
Scanning 9 generated artifacts for integration points...
INTEGRATION CHECKLIST:
[1] Wire WAL into Storage
├── Source: src/storage/wal.rs (generated)
├── Target: src/storage/mod.rs (existing)
├── Action: Add `pub mod wal;` to mod.rs
├── Action: Import WAL in MmapStorage impl
└── Satisfies: RT-1, T3
[2] Add WAL feature flag
├── Source: src/storage/wal.rs (uses feature gate)
├── Target: Cargo.toml
├── Action: Add `wal = []` to [features] section
└── Satisfies: T3
[3] Wire MVCC into TransactionManager
├── Source: src/transaction/mvcc.rs (generated)
├── Target: src/transaction/mod.rs (existing)
├── Action: Add `pub mod mvcc;`
├── Action: Import MvccManager in Transaction impl
└── Satisfies: RT-2, B4
[4] Wire Checkpoint into Storage
├── Source: src/storage/checkpoint.rs (generated)
├── Target: src/storage/mod.rs (existing)
├── Action: Add `pub mod checkpoint;`
├── Action: Add CheckpointManager to MmapStorage
└── Satisfies: RT-1, TN1
[5] Wire BatchManager into MemoryManager
├── Source: src/memory/batch.rs (generated)
├── Target: src/memory/mod.rs (existing)
├── Action: Add `pub mod batch;`
├── Action: Add BatchManager field to MemoryManager
└── Satisfies: RT-5, B3
INTEGRATION SUMMARY:
├── Total integration points: 5
├── Auto-wireable: 3 (mod declarations)
├── Manual required: 2 (struct modifications)
└── Estimated changes: ~50 lines
COPY-PASTE COMMANDS:
# Add mod declarations (can be automated)
echo 'pub mod wal;' >> src/storage/mod.rs
echo 'pub mod checkpoint;' >> src/storage/mod.rs
echo 'pub mod mvcc;' >> src/transaction/mod.rs
echo 'pub mod batch;' >> src/memory/mod.rs
# Add feature flag
# Edit Cargo.toml [features] section:
# wal = []
Next: After integration, run /manifold:m5-verify to validate
Updates manifold with integration status:
{
"integration": {
"timestamp": "2026-04-04T00:00:00Z",
"iteration": 5,
"checklist": [
{
"id": "INT-1",
"source": "src/storage/wal.rs",
"target": "src/storage/mod.rs",
"action": "Add mod declaration",
"status": "pending",
"satisfies": ["RT-1", "T3"]
},
{
"id": "INT-2",
"source": "src/storage/wal.rs",
"target": "Cargo.toml",
"action": "Add feature flag",
"status": "pending",
"satisfies": ["T3"]
}
],
"summary": {
"total_points": 5,
"completed": 0,
"pending": 5
}
}
}
With --auto-wire, safe integrations are performed automatically:
Safe to auto-wire:
pub mod xyz;)pub use xyz::*;)Requires manual review:
.manifold/<feature>.json (or .yaml for legacy)--auto-wire, perform safe integrationsiterations[]manifold validate <feature> — fix any errors before proceeding/manifold:m5-verify after integrationIntegration produces a wiring checklist with copy-paste commands. Where the checklist requires a choice (e.g., "this artifact can wire into either route A or route B — which?"), use AskUserQuestion (or the agent-equivalent: numbered options for Gemini, labelled choices for Codex).
AskUserQuestion — it's a report. End with the suggested next command (/manifold:m5-verify <feature>).AskUserQuestion. Plain-prose "shall I proceed?" is the anti-pattern.See install/agents/interaction-rules.md for the canonical contract; the prompt-enforcer.ts hook injects the same rules at runtime as defence-in-depth.
| Thought | Reality |
|---|---|
| "The artifacts exist, so they're wired" | Existence is not integration — trace the seams. |
| "Auto-wire everything" | Only auto-wire what is provably safe; flag the rest for manual review. |
| "Integration done without a check" | Verify prerequisites before claiming anything is wired. |
Run manifold validate <feature> after updates. Shared directives (output format, interaction rules, validation) injected by phase-commons hook.
Backward reasoning from desired outcome. Derives required conditions by asking 'What must be TRUE?'
Verify ALL artifacts against ALL constraints. Produces a verification matrix showing coverage and gaps
Light mode: 3-phase workflow for simple changes. Use instead of full workflow for bug fixes, small features, or quick iterations.
Generate parallel execution plan from constraint network. Identifies waves, critical path, and bidirectional dependencies
Initialize a constraint manifold for a feature. Creates .manifold/<feature>.json + .manifold/<feature>.md
Interview-driven constraint discovery across 5 categories (business, technical, UX, security, operational)