feature-loop-harness-cli 0.1.0

package/templates/default/.flh/workflow/docs-spec.yml

@@ -0,0 +1,134 @@
+version: 1
+
+defaults:
+  required_status: completed
+  forbidden_tokens:
+    - "{{TODO"
+    - "TODO"
+    - "TBD"
+    - "PLACEHOLDER"
+  min_section_chars: 40
+
+documents:
+  mvp:
+    path: docs/MVP.md
+    purpose: "Template completed by the actual project to define MVP scope."
+    required_sections:
+      - "MVP Goal"
+      - "Target Users"
+      - "Core Problem"
+      - "In Scope"
+      - "Out of Scope"
+      - "Success Criteria"
+
+  architecture:
+    path: docs/ARCHITECTURE.md
+    purpose: "Template completed by the actual project to define system architecture."
+    required_sections:
+      - "System Overview"
+      - "Tech Stack"
+      - "Source Layout"
+      - "Package Layout"
+      - "Testing Strategy"
+      - "Modules"
+      - "Data Flow"
+      - "External Dependencies"
+      - "Runtime Environment"
+      - "Scaffold Policy"
+      - "Constraints"
+
+  source_layout:
+    path: docs/source-layout.yml
+    format: yaml
+    purpose: "Machine-readable source layout manifest generated during architecture design."
+    required_status: completed
+    required_yaml_fields:
+      - project.type
+      - project.package_manager
+      - project.workspace
+      - project.runtime
+      - project.persistence.database_required
+      - project.persistence.database_provider
+      - source_roots
+    required_yaml_mapping: source_roots
+    required_yaml_mapping_item_fields:
+      - path
+      - role
+      - package
+      - stack
+      - framework
+      - runtime
+      - language
+      - module
+      - testing
+      - tooling
+      - scaffold
+      - description
+
+  feature_index:
+    path: docs/features/feature-index.md
+    purpose: "Template completed by the actual project to list feature candidates and priorities."
+    required_sections:
+      - "Feature Index"
+      - "Feature List"
+    required_item_fields:
+      - "Feature ID"
+      - "Name"
+      - "Summary"
+      - "Priority"
+      - "Core Requirements"
+
+  db_schema:
+    path: docs/DB_SCHEMA.md
+    purpose: "Template completed by the actual project to define a Prisma-ready data model baseline."
+    required_sections:
+      - "Core Entities"
+      - "Entity Specifications"
+      - "Relation Specifications"
+      - "Indexes and Constraints"
+      - "Enums"
+      - "Ownership and Permissions"
+      - "ID Strategy"
+      - "Lifecycle Policy"
+      - "Common Field Policy"
+      - "Prisma Mapping Notes"
+      - "Migration Notes"
+
+  api:
+    path: docs/API.md
+    purpose: "Template completed by the actual project to define API boundaries."
+    required_sections:
+      - "API Areas"
+      - "Endpoint Draft"
+      - "Authentication and Authorization"
+      - "Request and Response Rules"
+      - "Error Response Rules"
+
+  design:
+    path: docs/DESIGN.md
+    purpose: "Design guideline file for the actual project. It may be authored in this workflow or imported from an external source and approved in STATE.md."
+    required_sections:
+      - "Layout Principles"
+      - "Component Principles"
+      - "State Loading and Error"
+      - "Form Rules"
+      - "Responsive Rules"
+      - "Accessibility"
+
+  feature_implementation_pipeline:
+    path: .flh/docs/FEATURE_IMPLEMENTATION_PIPELINE.md
+    purpose: "Harness operation document for feature-level implementation."
+    required_status: completed
+    required_sections:
+      - "Overview"
+      - "Feature State Directories"
+      - "0. Preparation"
+      - "1. Design"
+      - "1.5. Source Package Scaffold Baseline"
+      - "1.6. Baseline DB Deployment"
+      - "2. Branch and Worktree"
+      - "3. Implementation and Tests"
+      - "4. Verification"
+      - "Quality Scoring"
+      - "5. Feedback Loop"
+      - "6. Commit Merge and Cleanup"

package/templates/default/.flh/workflow/flow.yml

@@ -0,0 +1,82 @@
+version: 1
+
+initial_state: MVP_DEFINITION
+
+states:
+  MVP_DEFINITION:
+    description: "Define the actual project's MVP using docs/MVP.md."
+    allowed_request_types:
+      - MVP_DESIGN_REQUEST
+      - STATE_STATUS_REQUEST
+      - STATE_TRANSITION_REQUEST
+      - UNKNOWN
+    next_states:
+      - ARCHITECTURE_DESIGN
+
+  ARCHITECTURE_DESIGN:
+    description: "Define the actual project's system architecture and source layout using docs/ARCHITECTURE.md and docs/source-layout.yml."
+    allowed_request_types:
+      - ARCHITECTURE_DESIGN_REQUEST
+      - STATE_STATUS_REQUEST
+      - STATE_TRANSITION_REQUEST
+      - UNKNOWN
+    next_states:
+      - FEATURE_INDEX_DEFINITION
+
+  FEATURE_INDEX_DEFINITION:
+    description: "Define the actual project's feature index using docs/features/feature-index.md."
+    allowed_request_types:
+      - FEATURE_INDEX_REQUEST
+      - STATE_STATUS_REQUEST
+      - STATE_TRANSITION_REQUEST
+      - UNKNOWN
+    next_states:
+      - DATA_MODEL_DEFINITION
+
+  DATA_MODEL_DEFINITION:
+    description: "Define the actual project's Prisma-ready data model baseline in docs/DB_SCHEMA.md without creating Prisma files."
+    allowed_request_types:
+      - DATA_MODEL_DESIGN_REQUEST
+      - PRISMA_BASELINE_CREATE_REQUEST
+      - STATE_STATUS_REQUEST
+      - STATE_TRANSITION_REQUEST
+      - UNKNOWN
+    next_states:
+      - API_DESIGN
+
+  API_DESIGN:
+    description: "Define the actual project's API boundaries using docs/API.md."
+    allowed_request_types:
+      - API_DESIGN_REQUEST
+      - STATE_STATUS_REQUEST
+      - STATE_TRANSITION_REQUEST
+      - UNKNOWN
+    next_states:
+      - FRONTEND_DESIGN
+
+  FRONTEND_DESIGN:
+    description: "Confirm the actual project's design guide using docs/DESIGN.md or STATE approvals.design."
+    allowed_request_types:
+      - FRONTEND_DESIGN_REQUEST
+      - STATE_STATUS_REQUEST
+      - STATE_TRANSITION_REQUEST
+      - UNKNOWN
+    next_states:
+      - FEATURE_IMPLEMENTATION
+
+  FEATURE_IMPLEMENTATION:
+    description: "Run feature-level implementation using .flh/docs/FEATURE_IMPLEMENTATION_PIPELINE.md."
+    allowed_request_types:
+      - FEATURE_PREPARE_REQUEST
+      - FEATURE_DESIGN_REQUEST
+      - IMPLEMENTATION_REQUEST
+      - TEST_REQUEST
+      - COMMIT_REQUEST
+      - STATE_STATUS_REQUEST
+      - UNKNOWN
+    next_states: []
+
+unknown_request_policy:
+  allow_without_state_transition: true
+  allowed_behavior: "Answer explanation, analysis, status, and documentation requests. File changes are limited by AGENTS.md."
+  forbidden_behavior: "Do not modify app/src/apps code, create tests, run implementation pipeline, commit, or update STATE.md."

package/templates/default/.flh/workflow/request-patterns.yml

@@ -0,0 +1,265 @@
+version: 1
+
+# Hook-level bypass patterns.
+# These are evaluated before workflow request patterns.
+# Pure question/confirmation prompts are treated as non-mutating requests.
+# If a prompt also contains another workflow intent, the hook treats it as low confidence.
+question_or_confirmation_patterns:
+  - \?
+  - 맞아\??$
+  - 맞나\??$
+  - 되나\??$
+  - 되는거지\??$
+  - 하면 되는거지\??$
+  - 해야 하나\??$
+  - 해도 돼\??$
+  - 괜찮아\??$
+  - "어떻게 생각"
+  - "어때"
+  - "맞을까"
+  - "좋을까"
+  - 수정하면 되는거지\??$
+  - 바꾸면 되는거지\??$
+  - 진행하면 되는거지\??$
+
+patterns:
+  PRISMA_BASELINE_CREATE_REQUEST:
+    strong:
+      - prisma.*baseline
+      - baseline.*prisma
+      - schema\.prisma
+      - 프리즈마.*베이스라인
+      - 프리즈마.*생성
+      - prisma.*생성
+    aliases:
+      - Prisma.*baseline.*만들
+      - schema\.prisma.*생성
+      - Prisma.*초기.*스키마
+      - Prisma.*모델.*생성
+      - DB.*baseline.*생성
+      - 초기.*migration
+      - baseline.*migration
+      - Prisma.*migration.*준비
+
+  IMPLEMENTATION_REQUEST:
+    strong:
+      - 구현해
+      - 코드.*작성
+      - 컴포넌트.*만들
+      - api.*구현
+      - 파일.*수정
+      - 앱.*수정
+      - 작업.*진행
+    aliases:
+      - 이.*기능.*구현
+      - 개발.*시작
+      - 코드.*반영
+      - 실제.*코드.*작성
+      - 앱.*반영
+      - 기능.*붙
+      - 화면.*만들
+      - API.*만들
+      - 컴포넌트.*만들
+      - 로직.*작성
+      - 수정.*반영
+
+  TEST_REQUEST:
+    strong:
+      - 테스트.*작성
+      - 테스트.*실행
+      - e2e
+      - unit test
+      - 유닛
+    aliases:
+      - 테스트.*만들
+      - 테스트.*추가
+      - 검증해
+      - 테스트.*돌
+      - E2E.*만들
+      - 유닛.*테스트.*만들
+      - 통합.*테스트.*작성
+      - 테스트.*케이스.*코드
+
+  COMMIT_REQUEST:
+    strong:
+      - 커밋
+      - commit
+      - push
+      - 푸쉬
+      - merge
+      - 머지
+    aliases:
+      - PR.*만들
+      - 브랜치.*정리
+      - 작업.*마무리
+      - 후처리.*진행
+      - 변경사항.*올
+
+  FEATURE_PREPARE_REQUEST:
+    strong:
+      - 기능.*준비
+      - feature.*prepare
+      - backlog
+      - 기능.*디렉토리.*생성
+    aliases:
+      - 이.*기능.*준비
+      - 기능.*작업.*준비
+      - 기능.*문서.*공간
+      - feature.*workspace
+      - 작업.*대상.*올
+      - 기능.*ready
+      - feature-index.*추가.*준비
+
+  FEATURE_DESIGN_REQUEST:
+    strong:
+      - 기능.*설계
+      - SPEC\.md
+      - CHECKLIST\.md
+      - TEST_CASES\.md
+      - 기능.*스펙
+    aliases:
+      - 이.*기능.*설계
+      - 기능.*스펙.*작성
+      - SPEC.*작성
+      - 체크리스트.*만들
+      - 테스트.*케이스.*정리
+      - 구현.*전.*기능.*문서
+      - 기능.*요구사항.*정리
+      - 기능.*범위.*정리
+      - 기능.*완료.*기준
+
+  MVP_DESIGN_REQUEST:
+    strong:
+      - \bmvp\b
+      - MVP
+      - 엠브이피
+      - 최소.*제품
+      - 최소.*범위
+    aliases:
+      - 초기.*범위.*정리
+      - 1차.*출시.*범위
+      - 핵심.*범위
+      - 어디까지.*만들
+      - 가장.*먼저.*만들
+      - 필수.*기능.*추
+      - 첫.*버전.*범위
+      - 프로젝트.*목표.*정리
+      - 타겟.*사용자.*정리
+      - 해결.*문제.*정리
+
+  ARCHITECTURE_DESIGN_REQUEST:
+    strong:
+      - 아키텍처
+      - 아키텍쳐
+      - architecture
+      - 시스템.*구조
+    aliases:
+      - 전체.*구조
+      - 기술.*구조
+      - 프로젝트.*구조
+      - 폴더.*구조
+      - 소스.*구조
+      - 소스.*레이아웃
+      - source.*layout
+      - 패키지.*구조
+      - 모듈.*구조
+      - 레이어.*구조
+      - 서비스.*구성
+      - 백엔드.*프론트.*연결
+
+  FEATURE_INDEX_REQUEST:
+    strong:
+      - feature-index
+      - 기능.*목록
+      - 기능.*리스트
+      - Feature Index
+    aliases:
+      - 필요한.*기능.*정리
+      - 구현할.*기능.*뽑
+      - 기능.*리스트업
+      - 기능.*우선순위
+      - 기능.*인덱스
+      - MVP.*기능.*나
+      - 기능.*단위.*쪼
+      - 작업할.*기능.*정리
+
+  DATA_MODEL_DESIGN_REQUEST:
+    strong:
+      - 데이터.*모델
+      - DB_SCHEMA
+      - ERD
+      - E-R
+      - 엔티티
+      - schema
+    aliases:
+      - 데이터.*구조
+      - 테이블.*구조
+      - DB.*구조
+      - ER.*구조
+      - 관계.*정의
+      - 스키마.*초안
+      - 도메인.*모델
+      - 저장.*데이터
+      - Prisma.*모델.*방향
+
+  API_DESIGN_REQUEST:
+    strong:
+      - \bAPI\b
+      - api
+      - 엔드포인트
+      - endpoint
+    aliases:
+      - API.*목록
+      - 엔드포인트.*목록
+      - API.*스펙
+      - 요청.*응답.*구조
+      - 라우트.*구조
+      - 서버.*API.*설계
+      - 백엔드.*API.*설계
+      - API.*계약
+
+  FRONTEND_DESIGN_REQUEST:
+    strong:
+      - 프론트
+      - frontend
+      - FRONTEND
+      - 디자인.*지침
+      - UI.*지침
+    aliases:
+      - 화면.*설계
+      - UI.*방향
+      - 프론트.*구조
+      - 화면.*흐름
+      - 페이지.*구성
+      - 사용자.*플로우
+      - 디자인.*가이드
+      - 컴포넌트.*방향
+      - 레이아웃.*방향
+
+  STATE_STATUS_REQUEST:
+    strong:
+      - 현재.*상태
+      - 진행.*상황
+      - 다음.*할
+      - 남은.*작업
+      - 요약
+      - 상태.*알려
+    aliases:
+      - 어디까지.*됐
+      - 현재.*단계
+      - 뭐.*해야
+      - 뭐부터.*하면
+      - 다음.*작업.*추천
+
+  STATE_TRANSITION_REQUEST:
+    strong:
+      - 다음.*단계
+      - 전이
+      - 상태.*변경
+    aliases:
+      - 다음.*단계.*넘어
+      - 단계.*변경
+      - 단계.*완료.*처리
+      - workflow.*이동
+      - 이.*단계.*끝
+      - 다음.*상태.*바

package/templates/default/.flh/workflow/state-actions.yml

@@ -0,0 +1,117 @@
+version: 1
+
+usage:
+  rule: "Read only the entry for the current state."
+  purpose: "Short execution checklist for the active project workflow state."
+
+states:
+  MVP_DEFINITION:
+    required_outputs:
+      - docs/MVP.md
+    actions:
+      - Clarify MVP goal, target users, core problem, scope, non-goals, and success criteria.
+      - Update docs/MVP.md.
+      - Mark docs/MVP.md as completed only when the MVP scope is clear.
+    allowed_extra_writes: []
+    ask_user_when:
+      - MVP scope is broad, conflicting, or unclear.
+
+  ARCHITECTURE_DESIGN:
+    required_outputs:
+      - docs/ARCHITECTURE.md
+      - docs/source-layout.yml
+      - source directories listed in docs/source-layout.yml
+    actions:
+      - Decide project type, package manager, runtime stack, persistence need, database provider, testing tools, and source layout.
+      - Use docs/source-layout.yml as the required architecture decision checklist.
+      - Ask the user for any missing docs/source-layout.yml fields before marking architecture completed.
+      - Write docs/source-layout.yml.
+      - Record project-level persistence.database_required and persistence.database_provider decisions in docs/source-layout.yml.
+      - Record package-level framework, runtime, language, module, testing, and tooling decisions in docs/source-layout.yml.
+      - Record project.scaffold_extra_root_files in docs/source-layout.yml only when scaffold baseline needs root files outside the default scaffold categories.
+      - Create only the directories listed in docs/source-layout.yml.
+      - Add .gitkeep to empty source directories.
+      - Update docs/ARCHITECTURE.md.
+      - Do not scaffold framework code in this state.
+    allowed_extra_writes:
+      - docs/source-layout.yml
+      - app/**/.gitkeep
+      - apps/**/.gitkeep
+      - packages/**/.gitkeep
+    ask_user_when:
+      - Project type, workspace policy, package manager, runtime, language, module, persistence need, database provider, or source layout is unclear.
+      - Unit, integration, E2E, or component testing tools are unclear.
+      - Lint or format tooling is unclear.
+      - Multiple frontend/backend/package layouts are plausible.
+
+  FEATURE_INDEX_DEFINITION:
+    required_outputs:
+      - docs/features/feature-index.md
+    actions:
+      - Derive feature candidates from MVP and architecture.
+      - Assign feature ID, name, summary, priority, core requirements, dependencies, and reference.
+      - Keep implementation status out of feature-index.md.
+      - Do not create feature SPEC/CHECKLIST/TEST_CASES yet.
+    allowed_extra_writes: []
+    ask_user_when:
+      - Feature priority or MVP fit is unclear.
+
+  DATA_MODEL_DEFINITION:
+    required_outputs:
+      - docs/DB_SCHEMA.md
+    actions:
+      - Define the project-wide data model baseline in docs/DB_SCHEMA.md.
+      - Make docs/DB_SCHEMA.md detailed enough to convert directly into schema.prisma during Feature Implementation 1.6.
+      - Define entity fields, Prisma types, DB types, nullability, defaults, uniqueness, indexes, relations, enums, constraints, ownership, ID strategy, lifecycle, common fields, Prisma mapping notes, and migration notes.
+      - Do not create or modify schema.prisma, Prisma migrations, package.json, or backend package files in this state.
+      - Do not deploy to a real DB server in this state.
+    allowed_extra_writes:
+      - docs/DB_SCHEMA.md
+    ask_user_when:
+      - Database provider, persistence need, entity ownership, relation cardinality, field nullability, index strategy, enum values, or lifecycle policy is unclear.
+
+  API_DESIGN:
+    required_outputs:
+      - docs/API.md
+    actions:
+      - Define API areas and endpoint draft.
+      - Define authentication, authorization, request/response, and error response rules.
+      - Align API design with feature-index and DB schema when they exist.
+      - Do not implement API routes in this state.
+    allowed_extra_writes: []
+    ask_user_when:
+      - API boundary, auth model, or backend responsibility is unclear.
+
+  FRONTEND_DESIGN:
+    required_outputs:
+      - docs/DESIGN.md
+      - or .flh/runtime/STATE.md approvals.design.approved for external design guide
+    actions:
+      - Ask whether to import an external DESIGN.md or author docs/DESIGN.md.
+      - If authoring, complete docs/DESIGN.md.
+      - If importing, confirm user approval and record non-secret design approval metadata.
+      - Do not implement UI in this state.
+    allowed_extra_writes:
+      - .flh/runtime/STATE.md
+    ask_user_when:
+      - Design source is unclear.
+      - Existing DESIGN.md does not clearly represent the project design guide.
+
+  FEATURE_IMPLEMENTATION:
+    required_outputs:
+      - feature directory under docs/features/*
+    actions:
+      - Use .flh/docs/FEATURE_IMPLEMENTATION_PIPELINE.md for the first full implementation loop.
+      - Do not start a new feature when docs/features/active or docs/features/review contains a feature directory.
+      - Verify source package scaffold baseline before creating the first feature branch/worktree.
+      - If source scaffold approval is missing, run Source Package Scaffold Baseline before DB deployment and feature work.
+      - Use AGENTS.md review rules for docs/features/review patch requests.
+      - Verify database baseline status after scaffold baseline and before moving the first feature to active.
+    allowed_extra_writes:
+      - controlled by AGENTS.md and FEATURE_IMPLEMENTATION_PIPELINE.md
+    ask_user_when:
+      - No feature is selected.
+      - active or review already contains a feature.
+      - source scaffold approval is missing.
+      - source scaffold needs more information than docs/source-layout.yml provides.
+      - database baseline approval is missing for a DB-backed project, or no-database skip approval is missing for a project that does not require a DB.

package/templates/default/.flh/workflow/transition-guards.yml

@@ -0,0 +1,57 @@
+version: 1
+
+transitions:
+  MVP_DEFINITION_TO_ARCHITECTURE_DESIGN:
+    from: MVP_DEFINITION
+    to: ARCHITECTURE_DESIGN
+    required_docs:
+      - mvp
+
+  ARCHITECTURE_DESIGN_TO_FEATURE_INDEX_DEFINITION:
+    from: ARCHITECTURE_DESIGN
+    to: FEATURE_INDEX_DEFINITION
+    required_docs:
+      - architecture
+    required_source_layout_directories:
+      - source_layout
+
+  FEATURE_INDEX_DEFINITION_TO_DATA_MODEL_DEFINITION:
+    from: FEATURE_INDEX_DEFINITION
+    to: DATA_MODEL_DEFINITION
+    required_docs:
+      - feature_index
+
+  DATA_MODEL_DEFINITION_TO_API_DESIGN:
+    from: DATA_MODEL_DEFINITION
+    to: API_DESIGN
+    required_docs:
+      - db_schema
+
+  API_DESIGN_TO_FRONTEND_DESIGN:
+    from: API_DESIGN
+    to: FRONTEND_DESIGN
+    required_docs:
+      - api
+
+  FRONTEND_DESIGN_TO_FEATURE_IMPLEMENTATION:
+    from: FRONTEND_DESIGN
+    to: FEATURE_IMPLEMENTATION
+    required_docs:
+      - feature_implementation_pipeline
+    required_docs_any:
+      - design
+    required_approvals_any:
+      - design
+    required_directories:
+      - docs/features/backlog
+      - docs/features/ready
+      - docs/features/active
+      - docs/features/blocked
+      - docs/features/review
+      - docs/features/done
+      - docs/features/postponed
+
+guard_policy:
+  check_all_intermediate_transitions: true
+  file_existence_only_is_insufficient: true
+  document_completion_uses: .flh/workflow/docs-spec.yml

package/templates/default/.husky/pre-commit

@@ -0,0 +1,3 @@
+#!/usr/bin/env sh
+
+python3 .flh/scripts/pre_commit.py

package/templates/default/AGENTS.md

@@ -0,0 +1,44 @@
+# AGENTS.md
+
+## Core Routing
+
+- Always read `.flh/runtime/STATE.md` before choosing a workflow.
+- For project workflow work, read only the current state's entry from `.flh/workflow/state-actions.yml`.
+- Follow the current state's `actions`, `allowed_extra_writes`, and `ask_user_when`.
+- Do not perform implementation work unless `current_state` is `FEATURE_IMPLEMENTATION`.
+
+## Runtime State
+
+- Treat `.flh/runtime/STATE.md` frontmatter as the only machine-readable runtime workflow state.
+- When updating `.flh/runtime/STATE.md`, preserve the Markdown body unless the user explicitly asks to change the state guide.
+- When recording `approvals`, follow the approval recording guide in the Markdown body of `.flh/runtime/STATE.md`.
+- Do not record secrets, API keys, tokens, passwords, or connection strings in `.flh/runtime/STATE.md`.
+
+## Prefix Modes
+
+- `/q`: question mode. Answer only. Do not create, modify, delete, commit, push, merge, update state, or run workflow pipelines.
+- `/d`: documentation and harness-control mode.
+- `/d` may modify only documentation and harness-maintenance targets: `docs/`, `.flh/`, `AGENTS.md`, `README.md`, `.codex/`, `tests/hooks/`, `.husky/`, `package.json`, `package-lock.json`.
+- When editing package scripts, test config, or lint-staged config for the harness, target source extensions only; do not include design/harness document extensions such as `md`, `yml`, or `yaml` unless explicitly requested.
+- `/d` may commit or push only when the user explicitly requests it and every changed file is within the allowed documentation/harness targets.
+- `/d` must not merge.
+- `/d` may perform explicit workflow state skip/transition requests.
+- Do not skip `MVP_DEFINITION`, `ARCHITECTURE_DESIGN`, or `FEATURE_INDEX_DEFINITION`.
+
+## Feature Implementation
+
+- Run `.flh/docs/FEATURE_IMPLEMENTATION_PIPELINE.md` only when `current_state` is `FEATURE_IMPLEMENTATION` and the user explicitly asks for feature implementation.
+- If the user has not explicitly requested implementation, do not run the implementation pipeline; ask whether they want to start or continue feature implementation.
+- Before running the full implementation pipeline, inspect `docs/features/active/` and `docs/features/review/`.
+- If `docs/features/active/` contains a feature directory, tell the user there is already an active feature and ask whether to continue it, block it, or finish it before starting another feature.
+- If `docs/features/review/` contains a feature directory, do not run the full implementation pipeline; use the review patch rules.
+- Do not start a new feature when either `docs/features/active/` or `docs/features/review/` contains a feature directory.
+- For status, progress, or next-work questions, answer only; do not run the implementation pipeline.
+
+## Review Patch
+
+- If `docs/features/review/` contains a feature directory, user edit requests target that feature by default.
+- Use one `fix/*` review branch/worktree per review feature until the user explicitly approves completion.
+- Follow `.flh/docs/REVIEW_PATCH_PIPELINE.md` for review feature edits.
+- Do not run `.flh/docs/FEATURE_IMPLEMENTATION_PIPELINE.md` for review feature edits.
+- Move a feature from `docs/features/review/` to `docs/features/done/` only when the user explicitly approves completion.