appboypov/das-work-skills/setup-work-skills

Set up the project

Read workflow. Inspect the existing project instructions, planning configuration, domain glossary and decision records. Reuse them. Honour an explicit choice to work outside the framework or an advice-only request before creating or modifying .das-work.

1. Discover the authenticated Linear workspace, relevant team, existing projects, statuses, type labels and templates using linear. Establish only missing ownership choices with the user. Record stable identifiers and useful links in .das-work at the project root, following project context. Keep credentials in the authenticated connection.
2. Establish the intent folder and exactly one second-brain folder with the user. Inspect each destination for existing instructions and follow them before writing. Record labelled Intent folder and Brain folder entries in .das-work. Relative paths resolve from the defining .das-work rather than the working directory. Separate roots and nested folders are both supported.

Resolve the worktree folder through project context. Record the resolved Worktree folder entry in .das-work, preserving an existing user-selected location.

1. Read installed setup. Establish repo-local, store-only or store-optional planning through openspec-store. Install the das-work-schema schema from the installed workflow skill into the resolved planning root, select it in the existing configuration, and verify native schema validation. Initialize OpenSpec only when authorized and verify openspec context --json resolves the intended root.
2. Read the project's existing glossary and ADR organization. For a single domain, use CONTEXT.md and docs/adr/ when needed. For multiple actual domains, a context map links their own glossaries. Create a glossary or decision record when there is settled content to record, following domain-modeling.
3. Make the installed skill location and .das-work discoverable through the host's supported skill discovery and existing project instructions. Preserve unrelated instructions. Configure native Linear templates only when requested through template setup.
4. Verify skill discovery, runtime version, schema resolution, Linear access, configured intent and brain folders, the resolved worktree destination, and the selected planning root. Report actual locations and any missing capability.