/dev-cycle-frontend-react-native

Execute the React Native frontend development cycle for tasks in a markdown file or from a direct prompt.

Usage

/bee:dev-cycle-frontend-react-native [tasks-file] [options] [prompt]
/bee:dev-cycle-frontend-react-native [prompt]

Arguments

Argument	Required	Description
tasks-file	No*	Path to markdown file with tasks (e.g., docs/tasks/sprint-001-frontend.md)
prompt	No*	Direct instruction for what to implement (no quotes needed)

*Either tasks-file, prompt, or --resume is required.

Options

Option	Description	Example
--task ID	Execute only specific task	--task PROJ-123
--skip-gates	Skip specific gates	--skip-gates devops
--dry-run	Validate tasks without executing	--dry-run
--resume	Resume interrupted cycle	--resume

Prompt Modes

Direct Prompt (No Tasks File)

When a prompt is provided without a tasks file, bee:dev-cycle-frontend-react-native enters prompt-only mode:

1. Analyzes the prompt to understand what needs to be done
2. Generates tasks internally (similar to pre-dev but streamlined)
3. Executes through 9 gates as normal

# Direct prompt - no tasks file needed
/bee:dev-cycle-frontend-react-native Implement home screen with transaction list and balance card

# Another example
/bee:dev-cycle-frontend-react-native Add settings screen with user profile, preferences, and notification controls

With Tasks File + Additional Context

# Tasks file with additional context
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md Focus on accessibility

# Tasks file with specific guidance
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md Use sindarian-rn DataTable for transaction list

Prompt Behavior (with tasks file)

CANNOT override CRITICAL gates. Provides custom context to agents.

Persistence:

• Stored: custom_prompt field in docs/bee:dev-cycle-frontend-react-native/current-cycle.json
• Resume: Survives interrupts; editable by modifying state file before --resume
• Reports: Included in execution reports under "Custom Context Used"

Propagation: Prepended to all agent prompts in a dedicated **CUSTOM CONTEXT (from user):** section. Applies to all gates and all agent types.

Constraints:

• Length: Recommended 50-75 words (~300-400 chars); hard limit 500 chars (truncated with warning).
• Sanitization: Whitespace trimmed, control chars stripped (except newlines), unicode normalized.

Gate Protection:

CRITICAL: Gates 2, 3, 6, 7, 8 enforce mandatory requirements:

• MUST enforce 0 VoiceOver/TalkBack violations (Gate 2 Accessibility)
• MUST enforce 85% coverage (Gate 3 Unit Testing)
• MUST enforce performance thresholds (Gate 6 Performance)
• MUST dispatch all 5 reviewers (Gate 7 Review)
• MUST require user approval (Gate 8 Validation)

View/modify persisted prompt:

jq '.custom_prompt' docs/bee:dev-cycle-frontend-react-native/current-cycle.json  # View
# Edit state file, then: /bee:dev-cycle-frontend-react-native --resume

Examples

# Direct prompt - implement React Native screen
/bee:dev-cycle-frontend-react-native Implement home screen with transaction list and real-time balance

# Direct prompt - another example
/bee:dev-cycle-frontend-react-native Add user settings screen with profile, preferences, and notifications

# Execute all tasks from a file
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md

# Execute single task
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md --task FE-001

# Skip DevOps setup (EAS Build already configured)
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md --skip-gates devops

# Validate tasks without executing
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md --dry-run

# Resume interrupted cycle
/bee:dev-cycle-frontend-react-native --resume

# Tasks file with additional context
/bee:dev-cycle-frontend-react-native docs/tasks/sprint-001-frontend.md Prioritize accessibility and use FlashList for all list screens

Prerequisites

1. Task file or prompt: Either a markdown file generated by /pre-dev-* or a direct prompt
2. Project standards (optional but recommended): docs/PROJECT_RULES.md with project conventions
3. PRD/TRD (optional): If exists in docs/pre-dev/{feature}/, will be used in design phase
4. Backend handoff (optional): If backend dev cycle completed, handoff provides endpoints and contracts

Gates Executed

Gate	Skill	Description
0	bee:dev-implementation	Implement code (TDD)
1	bee:dev-frontend-accessibility-react-native	VoiceOver/TalkBack compliance
2	bee:dev-unit-testing	Unit tests with 85%+ coverage (RNTL + Jest)
3	bee:dev-frontend-visual-react-native	Snapshot testing (all states, iOS + Android)
4	bee:dev-frontend-e2e-react-native	E2E tests with Detox (iOS + Android)
5	bee:dev-frontend-performance-react-native	Bundle size + FlashList + Hermes + image optimization
6	bee:requesting-code-review	Code review (5 reviewers in parallel)
7	bee:dev-validation	Final validation

Note: Tasks are loaded at initialization, not as a separate gate. All 8 gates are MANDATORY.

After all tasks: bee:dev-feedback-loop generates metrics report.

Output

• State file: docs/bee:dev-cycle-frontend-react-native/current-cycle.json
• Feedback report: docs/dev-team/feedback/cycle-frontend-react-native-YYYY-MM-DD.md

Related Commands

Command	Description
/bee:dev-cycle	Backend development cycle (8 gates)
/bee:dev-status	Check current cycle status
/bee:dev-cancel	Cancel running cycle
/bee:dev-report	View feedback report

---

MANDATORY: Load Full Skill

This command MUST load the skill for complete workflow execution.

Use Skill tool: bee:dev-cycle-frontend-react-native

The skill file is located at: skills/dev-cycle-frontend-react-native/SKILL.md

The skill contains the complete 9-gate workflow with:

• Anti-rationalization tables
• Pressure resistance scenarios
• TDD sub-phases (Gate 0.1 RED → Gate 0.2 GREEN)
• Gate completion definitions
• UI Library Mode Detection (sindarian-rn vs fallback)
• Backend Handoff Loading
• State management schema
• React Native hooks patterns and conventions
• Expo / bare React Native detection (when applicable)

Execution Context

Pass the following context to the skill:

Parameter	Value
tasks-file	First argument if it's a .md file path
prompt	Remaining text after tasks-file and options
--task	If provided, filter to specific task ID
--skip-gates	If provided, list of gates to skip
--dry-run	If provided, validate only
--resume	If provided, resume from existing state file

Argument Parsing:

• If first argument ends with .md → treat as tasks-file
• If first argument is an option (--*) → no tasks-file
• Remaining non-option text → prompt

Step 1: ASK EXECUTION MODE (MANDATORY)

After loading skill and before executing gates, you MUST ask:

AskUserQuestion:
  questions:
    - question: "Select execution mode for this React Native frontend cycle"
      header: "Mode"
      options:
        - label: "Manual per subtask"
          description: "Checkpoint after each subtask"
        - label: "Manual per task"
          description: "Checkpoint after each task"
        - label: "Automatic"
          description: "No checkpoints, run all gates"

Do not skip this. User hints ≠ mode selection. Only explicit selection is valid.

Quick Reference

See skill bee:dev-cycle-frontend-react-native for full details. Key rules:

• All 9 gates execute - Checkpoints affect pauses, not gates
• Gates execute in order - 0 → 1 → 2 → 3 → 4 → 5 → 6 → 7 → 8
• Gate 7 requires all 5 reviewers - 4/5 = FAIL
• Coverage threshold - 85% minimum, no exceptions
• VoiceOver/TalkBack compliance - 0 violations, no exceptions
• Performance thresholds - Bundle < 10% growth, Hermes enabled, FlashList for long lists
• State persisted - Can resume with --resume after any interruption
• React Native only - Functional components with hooks required; class components are a violation
• Platform-aware - If Platform.select() or .ios.tsx/.android.tsx patterns present, apply platform-specific conventions