onboarding-flow

Integrate Cursor Agent Factory into repositories with dry-run previews and conflict resolution.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gitwalter/cursor-agent-factory --skill onboarding-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboarding-flow
Source: https://github.com/gitwalter/cursor-agent-factory/tree/main/.cursor/skills/onboarding-flow
Command: npx skills add https://github.com/gitwalter/cursor-agent-factory --skill onboarding-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates Cursor Agent Factory into existing repositories non-destructively, preserving existing artifacts while adding missing components.

Core Features & Use Cases

  • Non-destructive onboarding of repos into Cursor Agent Factory
  • Dry-run previews to show what will be added or changed
  • Conflict resolution and backup guarantees
  • Optional Project Management setup for teams

Quick Start

Run analysis with: python cli/factory_cli.py --analyze <repo_path> Preview onboarding (dry run): python cli/factory_cli.py --onboard <repo_path> --dry-run Proceed with onboarding: python cli/factory_cli.py --onboard <repo_path>

Frequently Asked Questions about onboarding-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate an agent factory into an existing repository without losing custom files?

Non-destructive repository onboarding integrates the Cursor Agent Factory by enforcing backups and preserving existing artifacts while generating missing agents, skills, and templates. It ensures your custom files remain intact while adding required components.

Can I preview repository changes before committing to a full onboarding process?

Yes, you can preview onboarding changes using a dry-run. Running the CLI with the dry-run flag shows exactly what agents, skills, and documentation will be added or changed before any modifications are written to your repository.

What is the best way to handle conflicts when adding project management files to a repository?

Conflict resolution is built directly into the onboarding process. When integrating project management setups, the skill identifies overlapping configurations and resolves them systematically, ensuring existing repository structures are safely merged with new blueprints.

How do I analyze my repository to see what agents and knowledge files are missing?

You can analyze your repository by running the CLI with the analyze flag. This examines your project structure to determine which agents, knowledge files, templates, and documentation need to be generated during the onboarding rollout.

Does the onboarding process automatically update the CHANGELOG.md?

Yes, updating CHANGELOG.md is an automatic part of the onboarding process. As the skill generates missing agents, skills, and templates, it logs these structural changes and new configurations directly into your repository's changelog.