Results for “feature-request”

Implements a code change on a feature branch, opens a single pull request to main, and runs a code review loop before handoff.

Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.

Prove a feature works by delegating verification to an independent sub-agent that drives the real app, then open a pull request with the proof.

Turns a GitHub pull request into a code-change explainer video with changelog, feature reveal, or refactoring walkthrough built from the diff, commits, and files.

Triggers a code-review subagent after tasks, features, or before merging to catch issues early.

Create, list, and view GitHub issues using the gh CLI with guided workflows for gathering titles, descriptions, labels, and reproduction steps.

Use this when reviewing how a codebase organizes configuration files, env vars, runtime options, feature flags, and per-environment settings. Trigger on requests to clean up or validate config structure.

Creates GitHub Issues for unimplemented requirements from specification files, checking the codebase and existing issues to avoid duplicates.

Feature Intake

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Dispatches a code-reviewer subagent to evaluate work against requirements and plan, then acts on the feedback before merging.

Requesting Code Review

The pitch is often "a central place to store features," which undersells it into

Dispatch a code-reviewer subagent to catch issues before they cascade, with guidance on when to request review and how to act on feedback.

Systematically repair a broken feature or module by scoping, tracing dependencies, diagnosing all issues, fixing them in order, and verifying end-to-end.

Implements feature flags and remote configuration in Flutter apps using Firebase Remote Config and LaunchDarkly, enabling staged rollouts, A/B testing, and kill switches without app updates.

Organizes Flutter code by business features instead of technical layers, with self-contained folders for UI, logic, and data, plus a recommended project structure and dependencies.

Plan and implement new features, screens, managers, and systems in QuizVerse.

Use to fulfil a subject access request from support data — finding everything about the person, and deciding what must be redacted before disclosure. Trigger for "handle this SAR", "subject access request", "customer wants all their data", DSAR fulfilment from support systems, "a customer asked for their call recordings", or an employee requesting their own QA records.

Use when the user asks to fix, debug, or make a specific feature/module/area work end-to-end. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'. Not for quick single-bug fixes — this is for systematic deep-dive repair across all files and dependencies.

Imported skill api_feature from openai

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.

Generate a custom checklist for the current feature based on user requirements.

Use this when a feature or product needs a clear end-to-end user journey across entry, action, system response, and outcome. Trigger on requests to map the full experience before screens or components are finalized.

Retoma uma feature pausada (listada em paused-features de active-requirements.json) e a torna ativa. Use quando o usuário digitar "/reversa-resume", "reversa-resume", "retomar feature pausada" ou pedir para voltar a uma feature anterior. NÃO cria features novas, apenas troca a ativa pela escolhida e (quando faz sentido) move a ativa atual para paused-features.

Starts working on a new feature branch using git-flow. This skill should be used when the user asks to "start a feature", "create feature branch", "begin new feature", "git flow feature start", or wants to start a new feature. Accepts either a branch name or a natural-language description.

Creates a complete change proposal with design, specs, and tasks in one step, ready for implementation.

Use when user flows already exist and the team needs a screen inventory, screen responsibilities, key states, and view hierarchy for a product or feature. Trigger on requests to break a flow into pages, views, or screen-level structure.

Use when the team needs a clear product point of view, product principles, or a concise philosophy statement before planning UX, features, or architecture. Trigger on requests about product vision, differentiation, or what the product should optimize for.