From jaan-to
Integrates generated jaan-to outputs into project directories like src/, apps/, prisma/ with entry point wiring, validation, and dependency installation. Use when deploying generated code.
npx claudepluginhub parhumm/jaan-to --plugin jaan-toThis skill uses the workspace's default tool permissions.
> Bridge generated outputs from jaan-to/outputs/ into operational project locations.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Bridge generated outputs from jaan-to/outputs/ into operational project locations.
$JAAN_CONTEXT_DIR/tech.md — Tech stack (determines package manager, monorepo tool)
#current-stack, #frameworks, #constraints$JAAN_CONTEXT_DIR/config.md — Project configuration$JAAN_TEMPLATES_DIR/jaan-to-dev-output-integrate.template.md — Integration log template$JAAN_LEARN_DIR/jaan-to-dev-output-integrate.learn.md — Past lessons (loaded in Pre-Execution)${CLAUDE_PLUGIN_ROOT}/docs/extending/language-protocol.md — Language resolution protocolOutput Paths: $ARGUMENTS
MANDATORY — Read and execute ALL steps in: ${CLAUDE_PLUGIN_ROOT}/docs/extending/pre-execution-protocol.md
Skill name: dev-output-integrate
Execute: Step 0 (Init Guard) → A (Load Lessons) → B (Resolve Template) → C (Offer Template Seeding)
Also read context files if available:
$JAAN_CONTEXT_DIR/tech.md — Know the tech stack for framework-specific integration$JAAN_CONTEXT_DIR/config.md — Project configurationRead and apply language protocol: ${CLAUDE_PLUGIN_ROOT}/docs/extending/language-protocol.md
Override field for this skill: language_dev-output-integrate
Language exception: Generated code output (variable names, code blocks, schemas, SQL, API specs) is NOT affected by this setting and remains in the project's programming language.
ultrathink
Use extended reasoning for:
If $ARGUMENTS provided:
If empty (interactive mode):
$JAAN_OUTPUTS_DIR/**/*-readme.md for available outputsUse AskUserQuestion:
For each selected output:
{id}-{slug}-readme.mdcp commands → source and destination pairsfile.ts → src/file.ts) → mapping pairsFor each destination file:
Reference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/dev-output-integrate-reference.mdsection "Config Merge Strategies" for package.json deep merge and tsconfig.json extends patterns.
Parse READMEs for required modifications to existing files:
Build ordered list of Edit operations needed.
Reference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/dev-output-integrate-reference.mdsection "Entry Point Wiring Patterns" for Fastify plugin order, Next.js config, and provider registration.
Read $JAAN_CONTEXT_DIR/tech.md #current-stack to determine the framework routing convention.
For each output file, classify as:
For route-level files:
Reference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/dev-output-integrate-reference.mdsection "Route File Wiring" for per-stack detection tables and wiring rules.
When integrating outputs that include *-orval-config.ts or *-msw-* files:
orval.config.ts at project root (from {id}-{slug}-orval-config.ts)src/mocks/handlers.ts (from {id}-{slug}-msw-handlers.ts)src/mocks/browser.ts (from {id}-{slug}-msw-browser.ts)src/mocks/server.ts (from {id}-{slug}-msw-server.ts).storybook/preview.{ts,tsx,js,mjs,cjs}import { initialize, mswLoader } from 'msw-storybook-addon').storybook/preview.ts with MSW setupnpx msw init public/ --save to install the service worker"generate:api": "orval --config ./orval.config.ts" to scripts sectionReference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/openapi-integration-reference.mdfor Storybook preview setup patterns and flat output conventions.
Group operations by type:
INTEGRATION PLAN
================
NEW FILES ({count})
-------------------
{list with destination paths}
REPLACEMENTS ({count}) ⚠ will overwrite existing files
------------------------------------------------------
{list with source → destination + conflict note}
MERGES ({count})
----------------
{list with merge strategy description}
ENTRY POINT MODIFICATIONS ({count})
------------------------------------
{list with file + description of change}
ROUTE FILE WIRING ({count})
----------------------------
{list with source → route destination + framework convention}
DIRECTORIES TO CREATE ({count})
-------------------------------
{list}
TOTAL: {count} operations
Use AskUserQuestion:
Do NOT proceed to Phase 2 without explicit approval.
mkdir -p)For each entry point modification:
Reference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/dev-output-integrate-reference.mdsection "Security Plugin Registration Order" for the required order: helmet → CORS → rate-limit → session → CSRF → sensible.
Modification order:
Reference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/dev-output-integrate-reference.mdsection "Package Manager Detection" for lockfile-based detection table.
If approved: run {package_manager} install
Reference: See
${CLAUDE_PLUGIN_ROOT}/docs/extending/dev-output-integrate-reference.mdsection "Bootstrap Validation Sequence" for the install → generate → migrate → seed → build → verify sequence.
Run validation checks based on what was integrated:
npx tsc --noEmit (if .ts files copied)pnpm run lint (if lint script available)pnpm run test (if test files copied)Present results:
VALIDATION RESULTS
==================
TypeScript: ✓ Pass / ✗ {error count} errors
Lint: ✓ Pass / ✗ {warning count} warnings
Tests: ✓ Pass / ✗ {failure count} failures / ⊘ Skipped
File Operations:
Entry Points:
Route Wiring:
#current-stack frameworkValidation:
If any check fails, fix before proceeding.
source "${CLAUDE_PLUGIN_ROOT}/scripts/lib/id-generator.sh"
SUBDOMAIN_DIR="$JAAN_OUTPUTS_DIR/dev/output-integrate"
mkdir -p "$SUBDOMAIN_DIR"
NEXT_ID=$(generate_next_id "$SUBDOMAIN_DIR")
slug="{integration-slug}"
OUTPUT_FOLDER="${SUBDOMAIN_DIR}/${NEXT_ID}-${slug}"
Preview:
Output Configuration
- ID: {NEXT_ID}
- Folder:
$JAAN_OUTPUTS_DIR/dev/output-integrate/{NEXT_ID}-{slug}/- Main file:
{NEXT_ID}-{slug}.md
Use template from: $JAAN_TEMPLATES_DIR/jaan-to-dev-output-integrate.template.md
Write {NEXT_ID}-{slug}.md with:
git stash or git checkout -- {files})Update index:
source "${CLAUDE_PLUGIN_ROOT}/scripts/lib/index-updater.sh"
add_to_index \
"$SUBDOMAIN_DIR/README.md" \
"$NEXT_ID" \
"${NEXT_ID}-${slug}" \
"{Integration Title}" \
"{Executive summary — 1-2 sentences}"
Confirm:
Integration log written to:
$JAAN_OUTPUTS_DIR/dev/output-integrate/{NEXT_ID}-{slug}/{NEXT_ID}-{slug}.mdIndex updated:$JAAN_OUTPUTS_DIR/dev/output-integrate/README.md
Write .last-integration-manifest to $JAAN_OUTPUTS_DIR/:
MANIFEST_PATH="$JAAN_OUTPUTS_DIR/.last-integration-manifest"
The manifest contains one file path per line (relative to project root), listing ALL files currently in $JAAN_OUTPUTS_DIR/ at the time of integration.
Exclude from manifest:
$JAAN_OUTPUTS_DIR/dev/output-integrate/ (integration logs, not source outputs).last-integration-manifest)README.md index filesUse Glob to scan $JAAN_OUTPUTS_DIR/**/* and write the filtered list.
This enables the integration-drift-check hook to detect outputs created after this run.
Output integration complete!
Immediate Steps:
- Run
pnpm devto verify the application starts- Run
pnpm testfor the full test suite- Review any validation warnings above
- Commit your changes
Next Skills in Pipeline:
- Run
/jaan-to:detect-dev --incrementalto re-audit integrated files for security and quality findings- Run
/jaan-to:devops-deploy-activateif CI/CD configs were integrated- Run
/jaan-to:qa-test-generateto generate tests for integrated code- Run
/jaan-to:release-iterate-changelogto document the integration- If API tooling was integrated: "Run
npx orvalto generate typed API client from spec"
Use AskUserQuestion:
If "Learn from this": Run /jaan-to:learn-add dev-output-integrate "{feedback}"
/jaan-to:devops-deploy-activate)backend-scaffold + frontend-scaffold + backend-service-implement + qa-test-generate + devops-infra-scaffold + sec-audit-remediate
|
v
dev-output-integrate
|
v
devops-deploy-activate
tech.md detection$JAAN_OUTPUTS_DIR path