Skip to content

Separate coding vs non-coding tasks in action-item publishing - #127

Closed
oai-coding-agent[bot] wants to merge 1 commit into
mainfrom
oai/issue-119
Closed

Separate coding vs non-coding tasks in action-item publishing#127
oai-coding-agent[bot] wants to merge 1 commit into
mainfrom
oai/issue-119

Conversation

@oai-coding-agent

Copy link
Copy Markdown
Contributor

Summary
Add guidelines to the plan mode prompt (prompt_plan.jinja2) to classify meeting action items as either coding tasks (which create GitHub issues) or non-coding follow-ups (which remain Jira-only or communication items).

Implementation Details

  • Inserted a new Action Item Classification section under ## Planning Outputs in prompt_plan.jinja2.
  • Updated test_instruction_builder.py to assert the presence of the new classification guidelines.

Assumptions Made

  • The plan mode (used for meeting-intelligence planning) is the correct place to surface these instructions.
  • Prompt-level guidance is sufficient to drive the agent's classification behavior.

Testing

  • Ran uv run pytest; added assertions in test_instruction_builder.py.
  • All tests pass.

closes #119

🤖 Generated with OAI Coding Agent
Co-Authored-By: oai-coding-agent[bot] <214839426+oai-coding-agent[bot]@users.noreply.github.com>
@oai-coding-agent oai-coding-agent Bot added the oai label Jul 22, 2025
@mattmorgis
mattmorgis deleted the oai/issue-119 branch July 23, 2025 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Separate coding vs non-coding tasks in action-item publishing

1 participant