start

To get project orientation for a fresh AI coding session, invoke a read-only trigger that automatically discovers and summarizes temporal workflow docs like onboarding maps, DEVLOG entries, handovers, and task lists. This eliminates manual doc hunting and provides a concise state summary.

Automated markdown workflow discovery handles path assumptions by using glob searches across the project tree to locate workflow-related docs. This avoids errors from hardcoded paths and ensures all relevant onboarding maps, handover notes, and active task lists are found.

The best way to summarize current sprint status is by reading only the most relevant, up-to-date temporal docs like the latest DEVLOG entry and current handovers. This provides a concise project state summary and recommends the highest-priority next action without context bloat.

No, the project onboarding trigger is strictly read-only and docs-only. It never executes tests or writes files during session orientation; it solely reads markdown workflow documents to synthesize project context and suggest next steps.

You cannot use session orientation for deep periodic project audits or missing documentation. It delegates those specialized tasks to other workflow skills, focusing strictly on summarizing existing temporal markdown docs to eliminate session startup inertia.

You need a handover review at the start of a fresh AI coding session to instantly understand in-flight work, current sprint status, and pending tasks. It synthesizes current handover notes and active task lists to recommend your highest-priority next move.