---
name: flags
description: Use when you need to check feature flag states, compare channels, or debug why a feature behaves…
category: engineering
runtime: no special runtime
---

# flags output preview

## PART A: Task fit
- Use case: Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels. | Option | Purpose | |--------|---------| | (none) | Show all flags across all channels | | --diff <ch1> <ch2> | Compare flags between channels | | --cleanup | Show flags grouped by cleanup status | runs entirely locally. W….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Options / Channels / Legend” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels. | Option | Purpose | |--------|---------| | (none) | Show all flags across all channels | | --diff <ch1> <ch2> | Compare flags between channels | | --cleanup | Show flags grouped by cleanup status | runs entirely locally. W…”.
- **02** When the source has headings, the agent prioritizes “Options / Channels / Legend” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.