Skip to content

Proposals

Forge uses a lightweight proposal process for significant changes. Proposals live in the proposals/ directory of the repository.

Creating a Proposal

  1. Copy proposals/TEMPLATE.md to proposals/NNN-feature-name.md
  2. Fill in all sections
  3. Submit a PR for review and discussion

For smaller changes (bug fixes, default skill improvements), open a GitHub issue instead. Proposals are for changes that affect the core workflow, add new pipeline stages, or touch the system in ways that benefit from broad alignment first.

Proposal Lifecycle

Status Meaning
Draft Initial idea, not yet ready for review
Under Review Open for feedback and discussion
Accepted Approved for implementation
Rejected Not moving forward (rationale documented)
Implemented Feature built and merged

Index

# Title Status
001 Q&A Mode for Generated Artifacts Implemented
002 Workflow Status Updates in Jira Draft
003 Retryable Blocked State via forge:retry Implemented
004 Dynamic Skill Loading by Jira Project Implemented
005 CI Gate Skip via Comment Command Implemented
006 PR Description Sync After CI Fix Commits Implemented
007 Dedicated implement_review Node for PR Review Feedback Implemented
008 Stable PR-to-Ticket Association via State Lookup Draft
009 Skill Packages via Jira Project Metadata Draft
010 Repository Configuration via Jira Project Metadata Implemented