workflow-orientation

What problem does it solve?

Adopting the structured sprint-based human-training workflow in an existing project often risks disrupting established documentation conventions, overwriting team-curated files, or forcing incompatible structural changes. This Skill eliminates that risk by first auditing the project read-only to understand its current state before proposing any changes.

Core Features & Use Cases

• Read-Only State Detection: Classifies projects into 5 distinct states (empty, code with no workflow, partial setup, canonical healthy, mature divergent) without making any filesystem changes during the audit phase.
• Non-Destructive Adaptation: For projects with existing conventions, creates a bridging onboarding.md that maps to the project's actual files instead of imposing canonical human-training structure, preserving team workflows.
• Drift Checking for Healthy Projects: For projects already using the human-training workflow, runs automated checks for path resolution errors, stale DEVLOG entries, outdated handover docs, and missing template sections.
• Use Case: You have a mature open source project with its own CONTRIBUTING.md, docs folder, and release notes process. This Skill will create an onboarding.md that points to your existing files instead of overwriting them, so you can adopt the human-training workflow without disrupting your team's existing processes.

Quick Start

Invoke the workflow-orientation skill in your project to have the AI audit its current workflow state and propose a tailored, non-destructive plan for adopting the sprint-based human-training process.