daf-workflowlisted

# DevAIFlow Session Context Check the `DAF_SESSION_NAME` environment variable. If set, this is a managed DevAIFlow session — follow the initialization steps below. If not set, skip to the **Standalone Workflow Guide** section at the bottom. --- ## Session Initialization When `DAF_SESSION_NAME` is set, perform these steps **before doing any other work**: ### 1. Read Session Metadata ```bash daf info $DAF_SESSION_NAME ``` This shows: session name, goal, issue key, status, working directory, branch, workspace, session type, and conversation history. ### 2. Read Issue Tracker Ticket If `daf info` shows an issue key (e.g., `owner/repo#123` or `PROJ-456`), read the ticket using that key: ```bash # For GitHub issues (use the issue number from daf info) gh issue view <number> --comments # For GitLab issues glab issue view <number> --comments # For JIRA tickets (use the issue key from daf info) daf jira view <issue_key> --comments ``` Replace `<number>` or `<issue_key>` with the actual value shown in `daf info` output. ### 3. Read Context Files First, discover the DevAIFlow config directory by running `daf config show` and noting the parent directory of `config.json` from the "Configuration Files" section. Then read the hierarchical context files if they exist in that directory: - `ENTERPRISE.md` (enterprise-wide policies and standards) - `ORGANIZATION.md` (organization coding standards) - `TEAM.md` (team conventions and workflows) - `USER.md` (personal notes and prefe