Personal Feature Agent

Personal Feature Agent

[简体中文](README.zh-CN.md)

Personal Feature Agent is a Codex and Claude Code plugin that turns a small feature idea into a reviewed requirement, working code, and a verified development environment inside an existing repository.

It adds a deliberate workflow boundary between planning and coding: the agent may inspect the repository and revise the requirement, but the documented workflow does not permit product-code changes until you approve the exact SHA-256 digest of the current requirement document. This is an auditable collaboration rule for a cooperative agent, not a security boundary.

What it does

feature idea
    -> inspect repository evidence
    -> draft .feature-agent/requirement.md
    -> revise only the requested sections
    -> approve the exact requirement digest
    -> implement the feature
    -> build and test with repository-defined commands
    -> start a local or Docker development environment
    -> run an agent smoke test
    -> return an environment receipt

The workflow is designed for a person shipping a focused new feature. It keeps the specification lightweight, makes approval auditable, and records execution evidence in the target project rather than relying on chat history alone.

What it does not do

• It is not a bug-fixing, incident-response, or production-deployment agent.
• It does not replace product discovery, architecture review, security review, or human QA.
• It does not write to Jira or require Jenkins, a hosted service, or a dedicated UI.
• It does not automatically commit, push, merge, publish, or deploy to production.
• It does not invent build commands or report success without recorded evidence.

Approval gate

The requirement has a content digest. Approval is valid only for the exact digest shown by the agent. Editing the requirement after approval changes its digest and invalidates that approval.

This gate preserves the product workflow—review the requirement first, then d