Results for “scope”

Augment the standard ship lifecycle with monorepo package-scoped and transitive-dependent validation

按 scope 重置 wiki 到干净 scaffold（wiki / raw / log / checkpoints / all）。适用于开发迭代或 setup 失败后的无痛重启。

Creates custom ESLint rules using the ESLint RuleTester API and AST Explorer patterns, generating rule implementations with auto-fix suggestions based on estree node types and scope analysis.

Selects scoped architecture, backend, frontend, security, data, DevOps, QA, docs, performance, or product roles.

Draft product requirements with the problem, users, scope, requirements, metrics, and open decisions.

Tests OAuth 2.0 and OpenID Connect implementations for security flaws including authorization code interception, redirect URI manipulation, CSRF in OAuth flows, token leakage, scope escalation, and PKCE bypass.

Write a project charter that pins down goal, scope, success criteria, and stakeholders before work starts.

Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation.

Initializes or optimizes git-agent configuration, regenerates commit scopes from git history, and re-derives .gitignore rules.

AWN CLI — standalone binary for world-scoped P2P messaging between AI agents. Ed25519-signed, zero runtime dependencies.

Clarifies ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "grill me", ask hard questions, request relentless interrogation, pressure-test assumptions, clarify scope/requirements, define success criteria, or request system-design/optimization decisions.

Augment the standard exec lifecycle with monorepo detection, lane-spec generation, guard validation, and package-scoped dispatch

Write a Product Requirements Document structured with problem statement, goals, user stories, scope, and success metrics.

Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, scope design, and alignment with OAuth 2.1 security requirements.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.

Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.

Create change order templates for scope modifications. TRIGGERS - Use when user needs help with change-order related tasks.

Create change order templates for scope modifications. TRIGGERS - Use when user needs help with change-order related tasks.

Manage Binding entities — scoped, temporal, many-to-many relationships between v2 entity surfaces. Use when a relationship needs scope, time, or its own attributes — e.g. 'Alice is the tech lead for project X from Jan to June' or 'the security gate applies to this release WorkItem only on the main branch'.

Write construction bid proposals with scope and pricing. TRIGGERS - Use when user needs help with bid-proposal related tasks.

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Write construction bid proposals with scope and pricing. TRIGGERS - Use when user needs help with bid-proposal related tasks.

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

Close an approved plan with zero plan-related deferrals: implement every unfinished item, absorb every connected out-of-scope/follow-up/nice-to-have item parked by prior runs, fix. Use when a plan was marked done with work deferred, or the user says "complete everything", "don't defer", "fix out of scope too", "finish.

Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension.

Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension.

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Guides a structured planning pipeline for coding tasks, including scope detection, research, plan creation, and review.

Anti-over-engineering guardrail that activates when an AI coding agent expands scope, adds abstractions, or changes files the user did not request.

Anti-over-engineering guardrail that activates when an AI coding agent expands scope, adds abstractions, or changes files the user did not request.

Identifies, assesses, and mitigates risks at every phase of a development pipeline.

Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.

Anti-over-engineering guardrail that activates when an AI coding agent expands scope, adds abstractions, or changes files the user did not request.

Anti-over-engineering guardrail that activates when an AI coding agent expands scope, adds abstractions, or changes files the user did not request.