apply-agentflow-comments

name	apply-agentflow-comments
description	Apply open review comments to a Django AgentFlow proposal, revalidate app ownership and related contracts, and preserve immutable review history.

Apply Django AgentFlow Comments

Use this skill when the user asks to fix, address, resolve, or review AgentFlow comments. Change the architecture proposal, not Django implementation code.

Select The Proposal

Read repository rules, memories, .agentflow/AGENTFLOW.md, and .agentflow/references/django-architecture.md. Use the proposal or page named by the user. Otherwise inspect active proposals:

python3 .agentflow/scripts/agentflow.py proposal list

Do not combine unrelated proposals. Approved revisions are immutable; feedback that changes an approved Django architecture requires a new proposal.

Import And Read Open Comments

Always import pending browser operations and read every Open comment on the selected proposal:

python3 .agentflow/scripts/agentflow.py comment list <proposal-id> --status open

Read all comments when resolved history affects the same app, model, mixin, enum, endpoint, task, or schedule:

python3 .agentflow/scripts/agentflow.py comment list <proposal-id>

Resolved comments are immutable history. When feedback arrives in chat, record it against the narrowest stable page, navigation item, table row or cell, flow node or edge, or document section:

python3 .agentflow/scripts/agentflow.py comment add <proposal-id> \
  --page-id <page-id> \
  --element-type <column|row|cell|node|edge|group|section|block> \
  --element-id <element-id> \
  --message "<feedback>"

Use --navigation-id <id> for hierarchy feedback, or omit element arguments for the page.

Revise The Django Contract

1. Map every Open comment to a visible proposal change.
2. Reinspect source when the comment disputes existing behavior or Django ownership.
3. Preserve top-level app ownership; use Platform only for cross-app concerns.
4. Reconcile related pages when a comment changes a shared contract:
   • model fields, relations, constraints, and model mixins;
   • enum values and every represented consumer;
   • API decisions, persistence steps, responses, and task handoffs;
   • task states, retry behavior, Beat schedules, and outcomes.
5. Do not add unrelated cleanup or product behavior while making the architecture consistent.
6. Leave ambiguous, conflicting, blocked, or intentionally deferred comments Open and report why.

Revise the complete proposal and validate it:

python3 .agentflow/scripts/agentflow.py proposal revise <proposal-id> \
  --input /tmp/revised-proposal.json
python3 .agentflow/scripts/agentflow.py validate --proposal <proposal-id>

Resolve a comment only after the validated proposal visibly contains the requested result:

python3 .agentflow/scripts/agentflow.py comment resolve \
  <proposal-id> <comment-id> \
  --resolution "<specific Django architecture change>"

Re-list Open comments and submit only when none remain:

python3 .agentflow/scripts/agentflow.py comment list <proposal-id> --status open
python3 .agentflow/scripts/agentflow.py proposal submit <proposal-id>
make agentflow PROPOSAL=<proposal-id>

Do not open the generated page. Tell the user to refresh it.

Finish

• open means architecture work or a user decision remains.
• resolved means the validated proposal visibly addresses the comment.
• Only Open comments may be edited or deleted.
• Never edit proposal review files or .agentflow/comment-inbox/ manually.
• Store only durable Django architecture preferences in .agents/memory/architecture-feedback.md.

Report resolved comment IDs, remaining Open comments, and blockers. Stop before planning or implementation until the revised proposal is explicitly approved.