feat: add guided Agenova feature delivery skill - #2
wunderforge wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b8c8668c67
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 1. The repository's routing and contribution instructions. | ||
| 2. Current product and architecture contracts. | ||
| 3. The linked GitHub ticket. | ||
| 4. Its approved task packet and design specification. |
There was a problem hiding this comment.
Keep the ticket and approved packet co-authoritative
When an approved task packet refines or disagrees with the ticket, this precedence order tells the agent to follow the ticket and disregard the packet. That contradicts references/guided-workflow.md, which requires implementation to stop until the disagreement is resolved, and it can make delivery mode implement stale ticket text instead of the approved specification. Treat the ticket and packet as joint authorities whose conflicts require resolution rather than ranking one above the other.
Useful? React with 👍 / 👎.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Closes #1
What is shared?
The agenova-feature-delivery skill for Codex, Claude Code, and other Agent Skills-compatible clients. It guides one approved Agenova ticket through selective discovery, consequential design decisions, implementation, independent review, and evidence-backed verification.
Why is it reusable?
Agenova contributors need one repeatable workflow that keeps the GitHub ticket and task packet authoritative while making the useful feature-dev/AIDLC decision trail visible. Guided mode is for learning and review; delivery mode keeps the same gates with less narration.
What changed during design?
Security and evidence