commits
- Redesign ArPiDev and ArPiDoc into a V2 to reduce permanent prompt
context and better align with native coding-agent capabilities.
- Heavily simplify both `AGENTS.md` files: lean bootstrap, state-based
routing (framing/planning/execution/waiting/inconsistent), role
selection, standard response header, and backward-compatible artifact
parsing.
- Add explicit user-control guarantees: user override wins, pause is
always allowed after a story closes, visible reasoning in story logs,
one active story max, and optional commit proposals via `SPEC.md`.
- Clarify that the method does not replace native agent behavior
(IDE/chat history, diagnostics, diffs, `git status`, recent commits,
tool outputs).
- Strengthen role identity prompts (Architect / Pilot / Dev /
Documenter) with a concise “senior professional” framing plus
reflexes, anti-patterns, and escalation triggers.
- Simplify role instructions to a skills/training-first model: the
method orchestrates and preserves traceability instead of
over-prescribing how agents should code or document.
- Strengthen Pilot behavior with mandatory recon before drafting a story
(codebase inspection, local signals, web research only for unstable
external information), followed by story draft + QA.
- Redesign ArPiDev / ArPiDoc story artifacts into a core-first format:
minimal required fields for execution, evidence, and resume; optional
extended fields; incremental logs focused on what/why/verification.
- Refactor `SPEC.md` and `TASKS.md` into core-first guides with
essential sections only, and make `DECISIONS.md`, `CODEMAP.md`, and
custom doc models explicitly optional.
- Add explicit V1/V2/V2.1 compatibility rules: lenient parsing of older
`TASKS` and stories, minimal backfill only when required for safe
execution or closure.
- Require incremental Dev/Doc logs during execution (after each
meaningful integration/writing/check step), not only at the end.
- Require a short dated log note when a planned change is postponed or
dropped.
- Prevent handoff ping-pong by requiring a single effective handoff
announcement after story updates are complete.
- Extend orchestration intent to include explicit handoff requests and
"validate + stop/pause" user instructions.
- Add explicit Pilot pause flow:
- close validated story in-session,
- record pause decision in `Pilot exchange` (with date and resume
target),
- set `Active story: NONE (waiting on pending stories or user input)`
even if executable stories remain,
- do not auto-activate/create next story until user resumes.
- Align TASKS and STORY artifact guides with the same pause semantics
and traceability expectations.
Result: clearer execution trace, fewer non-actionable relay messages,
and predictable end-of-session closure when users pause work.
- Add mandatory request intent classification (execution, rework,
orchestration, framing) before role selection in both methods.
- Add intent overrides so orchestration/policy requests always stay with
Pilot, even when a story is active.
- Allow direct rework by Dev/Documenter when a story is in "Done,
Waiting for Validation" and user asks for changes.
- Add execution-role guards (Dev/Documenter) to escalate
orchestration/policy requests to Pilot instead of proceeding.
- Add Pilot-side rule to handle policy/process updates first without
handing off to execution roles.
- Keep execution responses actionable by preventing transition-only
handoff messages.
Result: smoother flow, fewer avoidable Pilot <-> Dev/Documenter
round-trips, and clearer ownership per request intent.
Adds a method-update migration path for missing required fields and
formalizes commit title/description/scope proposals driven by SPEC
policy.
- Introduces a dedicated **method drift** handling flow when existing
artifacts miss newly required fields.
- Adds **State H (Method drift / migration required)** in ArPiDev and
ArPiDoc AGENTS with a Pilot-led migration discussion/backfill process.
- Adds required-fields compliance scanning before normal state
classification, so schema drift is treated as method evolution (not
user error).
- Adds mandatory **Git and commit policy** sections to ArPiDev/ArPiDoc
SPEC templates (proposal required, owner, format, language, scope
strategy, examples).
- Updates Architect behavior to define commit/scope policy during
framing and persist it in SPEC.
- Adds story-level **Commit proposal** sections (title, description,
scopes, scope rationale), to be filled at `Done, Waiting for
Validation` when SPEC requires it.
- Updates Dev/Documenter and Pilot closure rules to enforce commit
proposal completeness and scope-policy alignment before `Done,
Validated`.
- Keeps DECISIONS focused on policy and migration changes rather than
per-story commit chatter.
Strengthens log quality rules so implementation and documentation
rationale is explicit, causal, and verifiable instead of vague.
Improves cross-method documentation tracking and removes empty
role-switch messages by requiring concrete execution in the same
response.
- Adds explicit ArPiDev -> ArPiDoc documentation intake signals (`To
document:`, `documentation impact`, `[DOC]`) and follow-up rules.
- Requires Pilot to ask whether validated Dev changes need ArPiDoc
updates, then record the decision and critical doc points.
- Adds dedicated story fields for documentation impact (Dev side) and
critical points to document (Doc side).
- Enforces a no-transition-only response rule: Dev/Documenter must
execute at least one concrete step instead of sending handoff-only
messages.
- Allows immediate execution when story status is `To Do, Validated` by
switching to `Active` and starting work in the same response.
- Keeps status/closure hygiene aligned with the new lifecycle and
pending-flow rules across both methods.
Adds a clean temporary-closure flow for blocked stories without breaking
the "single active story" rule.
- Introduces Parked as a valid story status (Active | Done | Parked).
- Adds required parked-story tracking fields: Blocker, Remaining work,
and Reopen when.
- Extends TASKS.md conventions with [PARKED], a Parked stories section,
and Active story: NONE (...) when no executable story is available.
- Updates Pilot and Dev role behavior to formalize parking handoff and
resume conditions.
- Updates AGENTS.md state detection with a dedicated Waiting / parked
state, separate from true inconsistency triage.
- Redesign ArPiDev and ArPiDoc into a V2 to reduce permanent prompt
context and better align with native coding-agent capabilities.
- Heavily simplify both `AGENTS.md` files: lean bootstrap, state-based
routing (framing/planning/execution/waiting/inconsistent), role
selection, standard response header, and backward-compatible artifact
parsing.
- Add explicit user-control guarantees: user override wins, pause is
always allowed after a story closes, visible reasoning in story logs,
one active story max, and optional commit proposals via `SPEC.md`.
- Clarify that the method does not replace native agent behavior
(IDE/chat history, diagnostics, diffs, `git status`, recent commits,
tool outputs).
- Strengthen role identity prompts (Architect / Pilot / Dev /
Documenter) with a concise “senior professional” framing plus
reflexes, anti-patterns, and escalation triggers.
- Simplify role instructions to a skills/training-first model: the
method orchestrates and preserves traceability instead of
over-prescribing how agents should code or document.
- Strengthen Pilot behavior with mandatory recon before drafting a story
(codebase inspection, local signals, web research only for unstable
external information), followed by story draft + QA.
- Redesign ArPiDev / ArPiDoc story artifacts into a core-first format:
minimal required fields for execution, evidence, and resume; optional
extended fields; incremental logs focused on what/why/verification.
- Refactor `SPEC.md` and `TASKS.md` into core-first guides with
essential sections only, and make `DECISIONS.md`, `CODEMAP.md`, and
custom doc models explicitly optional.
- Add explicit V1/V2/V2.1 compatibility rules: lenient parsing of older
`TASKS` and stories, minimal backfill only when required for safe
execution or closure.
- Require incremental Dev/Doc logs during execution (after each
meaningful integration/writing/check step), not only at the end.
- Require a short dated log note when a planned change is postponed or
dropped.
- Prevent handoff ping-pong by requiring a single effective handoff
announcement after story updates are complete.
- Extend orchestration intent to include explicit handoff requests and
"validate + stop/pause" user instructions.
- Add explicit Pilot pause flow:
- close validated story in-session,
- record pause decision in `Pilot exchange` (with date and resume
target),
- set `Active story: NONE (waiting on pending stories or user input)`
even if executable stories remain,
- do not auto-activate/create next story until user resumes.
- Align TASKS and STORY artifact guides with the same pause semantics
and traceability expectations.
Result: clearer execution trace, fewer non-actionable relay messages,
and predictable end-of-session closure when users pause work.
- Add mandatory request intent classification (execution, rework,
orchestration, framing) before role selection in both methods.
- Add intent overrides so orchestration/policy requests always stay with
Pilot, even when a story is active.
- Allow direct rework by Dev/Documenter when a story is in "Done,
Waiting for Validation" and user asks for changes.
- Add execution-role guards (Dev/Documenter) to escalate
orchestration/policy requests to Pilot instead of proceeding.
- Add Pilot-side rule to handle policy/process updates first without
handing off to execution roles.
- Keep execution responses actionable by preventing transition-only
handoff messages.
Result: smoother flow, fewer avoidable Pilot <-> Dev/Documenter
round-trips, and clearer ownership per request intent.
Adds a method-update migration path for missing required fields and
formalizes commit title/description/scope proposals driven by SPEC
policy.
- Introduces a dedicated **method drift** handling flow when existing
artifacts miss newly required fields.
- Adds **State H (Method drift / migration required)** in ArPiDev and
ArPiDoc AGENTS with a Pilot-led migration discussion/backfill process.
- Adds required-fields compliance scanning before normal state
classification, so schema drift is treated as method evolution (not
user error).
- Adds mandatory **Git and commit policy** sections to ArPiDev/ArPiDoc
SPEC templates (proposal required, owner, format, language, scope
strategy, examples).
- Updates Architect behavior to define commit/scope policy during
framing and persist it in SPEC.
- Adds story-level **Commit proposal** sections (title, description,
scopes, scope rationale), to be filled at `Done, Waiting for
Validation` when SPEC requires it.
- Updates Dev/Documenter and Pilot closure rules to enforce commit
proposal completeness and scope-policy alignment before `Done,
Validated`.
- Keeps DECISIONS focused on policy and migration changes rather than
per-story commit chatter.
Improves cross-method documentation tracking and removes empty
role-switch messages by requiring concrete execution in the same
response.
- Adds explicit ArPiDev -> ArPiDoc documentation intake signals (`To
document:`, `documentation impact`, `[DOC]`) and follow-up rules.
- Requires Pilot to ask whether validated Dev changes need ArPiDoc
updates, then record the decision and critical doc points.
- Adds dedicated story fields for documentation impact (Dev side) and
critical points to document (Doc side).
- Enforces a no-transition-only response rule: Dev/Documenter must
execute at least one concrete step instead of sending handoff-only
messages.
- Allows immediate execution when story status is `To Do, Validated` by
switching to `Active` and starting work in the same response.
- Keeps status/closure hygiene aligned with the new lifecycle and
pending-flow rules across both methods.
Adds a clean temporary-closure flow for blocked stories without breaking
the "single active story" rule.
- Introduces Parked as a valid story status (Active | Done | Parked).
- Adds required parked-story tracking fields: Blocker, Remaining work,
and Reopen when.
- Extends TASKS.md conventions with [PARKED], a Parked stories section,
and Active story: NONE (...) when no executable story is available.
- Updates Pilot and Dev role behavior to formalize parking handoff and
resume conditions.
- Updates AGENTS.md state detection with a dedicated Waiting / parked
state, separate from true inconsistency triage.