AI-SpecDoc AGENTS.md

Project Instructions

This file contains project-specific workflow and rules. Role-specific agent instructions live in the AI skill files; do not duplicate them here.

References

• Project docs index: docs/index.md
• Development workflow: docs/development.md
• Task management workflow: docs/task-management.md

Persistence Policy

• Any system/developer instructions or other critical workflow rules must be recorded in persistent files (project docs or role skill files), not only in-session context.
• When such instructions are discovered during a session, update the relevant files so a new session can resume without loss.

Git Workflow (Project)

Follow the repository Git rules in docs/development.md (branch naming, commit rules, merge policy).

Post-Completion Merge Request (Hard Stop)

• After successfully completing a task on a task branch (and committing task-related changes), the final response must explicitly request user approval to merge into main.
• Do not treat task completion, "finish", or a status summary as merge approval.
• Do not end a successful task handoff with only "done/completed" status; include a direct merge approval prompt (for example: "Approve merge to main?").

Agent Console Logs

• When switching skill modes during task work, emit a console message that states the current agent and who invoked it (e.g., "Console: feature-developer invoked by user.") so the terminal log captures the handoff.

Pre-flight Branch Check (Hard Stop)

• Before any code or configuration changes, confirm you are on a task branch (not main) and that it follows /-.
• Documentation files, AGENTS.md, and task files under tasks/** may be edited on main only for standalone documentation/process maintenance not tied to an active task.
• If the user starts or continues a task from tasks/active.json, create/switch to a task branch before any edits, even when the first edits are only in docs/** or tasks/**.
• Still run git branch --show-current and git status before edits; if task-related changes are needed while on main, create a task branch that follows the naming rule (default type to feat if unclear) and continue without asking for the branch name.
• If user edits are present in files you are about to modify for the current task, ask whether to keep or overwrite those edits before applying changes that could replace them.