Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
508 changes: 0 additions & 508 deletions .agents/roles.md

This file was deleted.

2 changes: 1 addition & 1 deletion .agents/rules/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This reference defines the DevLog-specific flow and boundaries for AI-assisted a

The goal is not to make the AI decide more architecture policy. The goal is to make the AI stop before it makes project-specific architecture decisions that should be confirmed by the user.

Use this reference with `AGENTS.md`, `.agents/rules/general.md`, and `.agents/roles.md`.
Use this reference with `AGENTS.md` and `.agents/rules/general.md`.

This repository is a Tuist-generated, workspace-based modular iOS app. There is no root `Package.swift`; module projects are generated from `Workspace.swift` and each module's `Project.swift`.

Expand Down
10 changes: 5 additions & 5 deletions .agents/rules/general.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
## Logic preservation and optimization

- Reuse the existing program logic as-is whenever possible.
- Change logic only when the new approach produces exactly the same result and strictly improves time or space complexity.
- If there is no clear complexity improvement, keep the original logic.
- Change logic when the user explicitly requests the behavior change, or when the new approach produces exactly the same result and strictly improves time or space complexity.
- Otherwise, keep the original logic.

## Code modification response style

Expand All @@ -20,10 +20,10 @@

## Documentation placement

- Keep AI workflow and rule documents under `.agents/`.
- Keep approved workflow Specs under `.agents/specs/`.
- Keep AI working rules under `.agents/rules/`.
- Treat existing files under `.agents/specs/` as historical records, not required inputs for new work.
- Keep `docs/` for README images and draw.io sources.
- Do not add AI workflow documents under `docs/`.
- Do not add AI working rules under `docs/`.

## Repository-local rules

Expand Down
6 changes: 0 additions & 6 deletions .agents/rules/project-workflows.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,6 @@ This reference holds DevLog-specific working rules that should live with the pro
- CI is build validation, not a full test run, unless the workflow changes.
- Avoid unrelated generated project and `Package.resolved` churn. Generated Xcode workspace/project files should not be tracked unless the project explicitly changes that policy.

## SDD execution authority

- An approved Spec records behavioral constraints, acceptance criteria, and prohibited actions.
- A `Task Packet` records role assignment and current-turn execution authority separately from the Spec.
- Record app or Simulator execution, external writes, CI or PR actions, and verification commands separately in both artifacts. Do not infer authorization from a Spec or a `Task Packet` field that does not grant it.

## Xcode project file work

- Inspect Swift imports and Tuist target dependencies together.
Expand Down
60 changes: 6 additions & 54 deletions .agents/specs/README.md
Original file line number Diff line number Diff line change
@@ -1,56 +1,8 @@
# DevLog Spec Format
# DevLog Spec 기록

`Designer Result`를 사용자가 승인한 뒤, Planner가 비단순 설계 또는 구현 작업마다 이 디렉터리에 Spec을 작성한다. 이슈 기반 작업은 `<issue-number>-<short-topic>.md`, 이슈 없는 사용자 요청은 `user-<YYYYMMDD>-<short-topic>.md` 형식을 사용한다.
이 디렉터리는 이전 작업에서 합의한 범위와 검증 기준을 보존하는 역사 자료다.

## Responsibility

- `Design Brief`는 Planner가 요청, 현재 상태, 범위, 제외 범위, 알려진 제약을 Designer에게 전달하는 입력이다.
- `Designer Result`는 Designer가 제약, 대안, 변경 경계, 수용 기준, 검증, 최소 커밋 단위를 분석한 승인 대기 결과다.
- Spec은 사용자가 승인한 `Designer Result`를 영속화한 구현·검토·검증의 공통 기준이다.
- `Task Packet`은 승인된 Spec 경로와 수용 기준을 참조하고, 현재 작업의 역할 배정과 실행 권한을 전달한다.

## Required format

```md
# <Spec title>

- Source:
- Approved Designer Result:
- User approval:

## Constraints

-

## Alternatives and decision

-

## Changed boundaries

-

## Acceptance criteria

- [ ]

## Verification

- Command:
- Evidence:

## Minimum commit units

1.

## Execution constraints

- app or Simulator execution:
- External writes:
- CI or PR actions:
```

## Change control

- 구현 중 요구 사항 또는 범위가 바뀌면 Spec을 수정하고 사용자 재승인을 받은 뒤에만 `Task Packet`과 구현을 갱신한다.
- Spec은 동작과 수용 기준, 금지된 실행을 기록한다. `Task Packet`은 역할별 현재 작업 권한과 실제 검증 명령을 별도로 기록한다.
- 기존 파일은 당시 작업의 판단 근거로만 사용한다.
- 새 작업을 시작하기 위한 필수 문서나 승인 절차로 사용하지 않는다.
- 현재 요청과 저장소 상태가 기존 기록과 다르면 현재 요청과 저장소 규칙을 우선한다.
- 기존 기록을 일괄 수정하거나 삭제하지 않는다.
Loading