Skip to content
cccskills
FreePublished on GitHub

feature-design

Choose a feature design using the relevant code, requirements, and existing conventions. Record the chosen approach, alternatives, risks, and coverage of key user journeys, and identify decisions that need human input before implementation.

OriginalShow the original description

Choose the design, record the alternatives and CUJ coverage, or stop when a choice needs a human.

omnigent-ai/omnigent
See how to install

Good for

  • Choose an implementation approach before coding
  • Document alternatives and reasons for rejecting them
  • Check coverage of key user journeys
  • Prepare options for decisions requiring human input

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Design

Read the code each requirement touches before choosing. Then record, for the PR and the handoff's design and cujs fields:

  • Chosen design: where it plugs in (layers, APIs, configuration, flags) and how each requirement is met. Follow the repository's existing patterns and CLAUDE.md.
  • Alternatives considered: each realistic alternative and why you rejected it. One or two well-argued alternatives beat a long list.
  • Risks: compatibility, migration, performance, and security concerns, and how the design handles them.
  • CUJ coverage: mark each CUJ covered or not covered. Every not-covered CUJ gets a reason (out of scope, needs a separate feature, blocked by a missing capability). Cover at least one CUJ.

Decide, or stop for a human

Make product and technical choices yourself when the ticket, code, docs, or existing conventions support one. Write the choice and the alternatives down; reviewers judge them on the PR.

Stop with needs_more_info before implementation only when a choice really needs a human decision, for example:

  • a product-design question the ticket leaves open and the product gives no basis to settle;
  • a technical choice that is hard to reverse, such as a public API, data model, or stored-format change, where the options trade off differently and nothing in the ticket or code favors one;
  • a ticket that contradicts existing behavior other users depend on.

In that case ticket_comment lays out the options, their tradeoffs, and your recommendation, so a human can answer on the ticket and rerun the agent. Small or easily reversed choices never justify stopping.

Then load feature-implement.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

antigravity-native-e2e-dev

FreeSummary

Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.

  • Testing message delivery from the web interface to agy
  • Checking terminal output against mirrored session replies
  • Verifying permission requests and interruption
omnigent-ai/omnigent10.9KUpdated Oct 18, 2026

antigravity-sdk-e2e-dev

FreeSummary

Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.

  • Test authentication and real Gemini responses
  • Verify tool connections and sub-agent delegation
  • Investigate model selection failures
omnigent-ai/omnigent10.9KUpdated Oct 18, 2026

api-docs

FreeSummary

Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.

  • Writing reference docs for a public module
  • Documenting command-line arguments and defaults
  • Adding minimal usage examples for an API
omnigent-ai/omnigent10.9KUpdated Oct 18, 2026

build-omnigent

FreeSummary

Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.

  • Creating a minimal Omnigent agent
  • Configuring an agent with web search
  • Adding shell access or MCP tool connections
omnigent-ai/omnigent10.9KUpdated Oct 18, 2026

changelog

FreeSummary

Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.

  • Write release notes covering changes since the last tag
  • Summarize pull requests merged during a selected period
  • Highlight breaking changes before an upgrade
omnigent-ai/omnigent10.9KUpdated Oct 18, 2026

cli-setup-verify

FreeSummary

Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.

  • Reproducing a first-run setup problem
  • Inspecting menus in a narrow terminal
  • Checking help text and command visibility
omnigent-ai/omnigent10.9KUpdated Oct 18, 2026

See all skills by omnigent-ai

Report a problem with this skill