Skill

quick

Quick task execution without a full plan — just do it and commit. Use this skill whenever the user says "/quick", "quick fix", "just do it", "small fix", or any request for a small change that doesn't need planning. Also triggers on "quick task", "small change", "tweak this", "simple fix", "rename this", "fix this typo", "update the config", "one-liner", "trivial change", "swap this", "change this value", "toggle this", or any 1-3 file change that doesn't warrant a full /plan workflow. Supports optional GitHub Issues integration for issue tracking.

npx claudepluginhub skaisser/blueprint-plugin

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Quick task execution. No plan, no team. Just do it and commit.

SKILL.md

Similar Skills

ui-ux-pro-max

72.7k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

51.8k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

competitive-landscape

32.9k

Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.

startup-business-analyst

Stats

Stars0

Forks0

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Quick: Fast Task Execution

Quick task execution. No plan, no team. Just do it and commit.

Language

Read blueprint/.config.yml → language. If auto, detect from the user's messages. All generated content MUST be in the detected language. Skill instructions stay in English — only output changes.

For small fixes, tweaks, and tasks that don't need a full planning workflow.

GitHub Issue Support

If $ARGUMENTS contains a GitHub issue reference (e.g., /quick #42, /quick issue 42, or a number that doesn't match a backlog item), parse the issue number:

Fetch issue details: gh issue view <NUMBER> --json title,body,labels
Use the issue title/body as context for the task
Track the issue number for the commit and PR steps

Process

Understand the task from $ARGUMENTS (including GitHub issue context if provided)
Clarify if ambiguous — AskUserQuestion ONLY if genuinely unclear
Read relevant files
Confirm approach — Brief one-liner (mention if referencing past plan)
Implement — Make the minimal change requested. Do not refactor, clean up, or improve surrounding code
Verify — Check the change is correct: no syntax errors, no broken references, run targeted tests if testable logic changed
Commit — Use /commit. If a GitHub issue was provided, include Closes #N in the commit message body
GitHub update — If issue ID provided: push and update status
Ask next — AskUserQuestion:
- "Yes, we're done"
- "Create a PR for this" — Run /pr (issue reference will be included in PR body)
- "More changes needed" — Continue on branch

Rules

No plan file, no team, no worktree, no subagents
No sequential thinking (keep it fast)
Stay on current branch unless user requests a new branch
Ask ONLY if genuinely ambiguous
Always confirm approach in one line before changing
Make only the change requested — do not refactor, clean up, or improve surrounding code
Follow existing codebase patterns and conventions
Run targeted tests — full suite: ask user to run separately
If changes would span more than 3 files, suggest /plan instead — quick is for small scope
Use /ship to commit and push

Use $ARGUMENTS as the task description.