itdove/devaiflow#352: Clarify daf active is only needed for development sessions, not analysis-only#355
Conversation
- Distinguish development sessions (daf open) from analysis-only sessions - Mark `daf active` as needed only for development sessions, not analysis - Add running `daf active` to critical first steps in development workflow - Update best practices and quick reference with development-session qualifier 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR does not need a corresponding Jira item.
Related Issue: #352
Description
This PR updates documentation in the daf-workflow skill to clarify when the
daf activecommand is required. The updated documentation specifies thatdaf activeis only needed for development sessions (those involving code changes, commits, and PRs), not for analysis-only sessions where users are simply exploring code or asking questions.This clarification helps users understand when they need to activate a DevAIFlow session versus when they can work directly without the additional session management overhead.
Assisted-by: Claude
Testing
Steps to test
devflow/cli_skills/daf-workflow/SKILL.mddaf activeScenarios tested
daf activecommand behaviorDeployment considerations