Results for “scope”

Discovers and invokes agent skills by mapping tasks to development phases, with core operating behaviors for assumption surfacing, confusion management, and scope discipline.

Analyze draft prompts to identify intent, scope, and missing context, then generate an optimized prompt with ECC component recommendations. Advisory only — never executes the task.

Shape, bet, and build products using the 37signals philosophy from Getting Real, Rework, and Shape Up — fix time, flex scope, and ship with small autonomous teams.

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

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.

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

Refines task prompts through iterative questioning about scope, deliverables, and constraints, then copies the final markdown to the clipboard.

Transforms lessons learned into domain-organized memory instructions that persist across VS Code contexts, with global and workspace scopes.

Trigger: project task list, task decomposition, phase planning, master orchestration, delivery governance. Scope: Project sequencing, task checklist creation, operating governance. Boundary: Excludes tactical code debugging.

Breaks complex problems into iterative reasoning steps with revision, branching, and dynamic scope adjustment for multi-stage analysis and planning.

Runs a structured five-round brainstorm to capture actors, features, scope, constraints, and business rules before writing a spec.

Creates Cursor rules in .cursor/rules/ with YAML frontmatter for persistent AI guidance, including scope and file pattern configuration.

Guides the creation of well-structured Claude Code skills and slash commands, covering skill types, scope, frontmatter settings, and file organization.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.

Use only for developer-facing tools, libraries, SDKs, CLIs, APIs, and infrastructure products

Guides structured problem-solving through iterative reasoning steps, with support for revising conclusions, branching into alternative approaches, and dynamically adjusting scope as understanding evolves.

Composite skill — land a safe first PR in an unfamiliar repo without rediscovery loops or guessing at conventions. Chains onboard-new-repo (architecture + scripts + CI scan) → context-pack (relevant files + standards + ADRs for the scoped change) → scope-and-execute (narrow the task) → test-driven-development (write failing test first) → pr-to-release (open the PR). Use the first time you contribute to a repo OR when an unfamiliar contributor needs a guided first change.

Identify, assess, and mitigate project risks across technical, scope, dependency, and timeline categories using a structured register and escalation rules.

Trigger: standard work, deming first, feedback loop checks, decision rights, delegation check. Scope: Engineering operating models, team governance, task feedback loops. Boundary: Excludes direct code implementation or design templates.

Use when deciding which jama-* sub-skill to invoke next, or when sequencing a clinical manuscript from scope check through revision for JAMA (Journal of the American Medical Association). Routes — does not replace — the specialized skills.

Formats git commits with Sentry-style conventional commit messages, including type, scope, subject, body, and issue references, and enforces branch safety by creating a feature branch when on main or master.

Use when finishing a task, before merging, or when giving or receiving code review feedback on this repo - covers when to request a review, how to scope it, and how to respond to feedback with technical rigor instead of reflexive agreement.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Integrate Microsoft Graph SDK into any project — .NET, TypeScript/JavaScript, or Python. Covers auth patterns (client credentials, OBO, managed identity), SDK setup, calling Graph APIs, batching, delta queries, change notifications, throttling, and permission scopes. Use when accessing Microsoft 365 data (users, mail, calendar, Teams, files, SharePoint) from any application type.

Generate implementation plans from approved designs — plan-generator, phase-based plans, parallel batch execution, task dependency graph, owner skill routing, acceptance criteria, global done criteria, plan frontmatter, layout contract, interaction contract, anti-drift rules, plan format, AD-2 byte-for-byte gate, scope definition, execution plan, phases and batches, task anatomy, plan file format