feature-devlisted

# Feature Development > Part of **Foundry**, an AI-native, spec-driven development suite. Role: Feature delivery (1 to N). Siblings: `coding-start`, `project-onboard`. ## Mission and Boundaries Advance exactly one selected Feature, Change, or Bug from fact confirmation to verifiable delivery. Follow project conventions. This Skill MUST NOT redesign the project baseline or absorb unrelated Features. Read-only code review, diagnosis/explanation only, ordinary code Q&A, and solution brainstorming are outside this Skill; use the matching read-only flow. `Review` denotes this lifecycle stage only after implementation of the selected work item. `Decision Authority` MUST be a named human empowered for the specific decision, such as a Maintainer, Roadmap, Product, or Architecture Decision Authority. The executing Agent, automation, and an implementation-only assignee MUST NOT approve their own requirement changes, risk waivers, alternative verification, L2/L3 impacts, or delivery standards. Record approver, source, time, and scope for every approval. Responsibility boundaries: - `Spec` defines what is correct. - `Issue/work item` records work status; it MUST NOT duplicate the full Spec. - `Implementation Plan` defines how to implement; it MUST NOT rewrite requirements. - `PR/delivery record` states what changed in code. - `ADR` records why a significant technical or architectural decision was made. - `AGENTS.md` stores durable project rules; this Skill stores the cross-project