skills.rest
selossebdc-cell
selossebdc-cellCOMMUNITY
Explore all skills by this author →
GitHub

factory-quick

Coordinate minor-change deliveries with BMAD Quick Flow validation and CHANGELOG recording.

Updated Aug 23, 2026
Search Tags:#automation#workflow#specs#bug-fix#quick-flow#minor-fix#ui-tweak
One-click install
npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-quick-selossebdc-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: factory-quick
Source: https://github.com/selossebdc-cell/portail-client-v2/tree/main/.claude/skills/factory-quick
Command: npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-quick-selossebdc-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BMAD Quick Flow orchestrates quick fixes for minor issues without a full pipeline, reducing cycle time and risk.

Core Features & Use Cases

  • Orchestrates a minimal change path for bug fixes, UI tweaks, and internal refactors.
  • Enforces lightweight validation against existing specs and delta analysis to keep changes scoped.
  • Facilitates quick decision paths (Quick OK or Quick Force) and automatic or guided production of task artifacts.

Quick Start

Initiate the BMAD Quick Flow for a minor change, implement the fix, and validate it against the existing specs.

Frequently Asked Questions about factory-quick

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a quick flow for shipping minor bug fixes and UI tweaks?▼

A quick flow is a minimal change path that orchestrates fast deliveries for minor bug fixes and UI tweaks without invoking a full development pipeline. It enforces lightweight validation against existing specs to keep changes scoped.

How do I automate a minor change workflow without a full pipeline?▼

You can automate a minor change workflow by initiating a quick flow, implementing the fix, and validating it against existing specs. It imposes tooling checks, delta analysis, and optional shortcuts to control scope and record changes.

Can I use a quick flow for refactoring if I have existing V1+ code?▼

Yes, you can use a quick flow for internal refactoring if you have existing V1+ code in src/ and clear specs in docs/specs. It is designed to validate minor changes without altering core domain models.

What is the difference between Quick OK and Quick Force in minor change workflows?▼

Quick OK and Quick Force are optional decision paths within the quick flow. They facilitate rapid validation and progression of task artifacts while enforcing tooling checks and delta analysis to control the minor change scope.

When should I not use a quick flow for bug fixes?▼

You should not use a quick flow when changes alter core domain models or exceed minor scope. It is strictly for bug fixes, UI tweaks, and internal refactors where existing specs and V1+ code remain fundamentally unchanged.

Related Skills

Explore More Software Engineering Skills→
kevinslinkevinslin
21

dev.research

Create structured research artifacts for codebase exploration with templates and workflows.

Community
Advanced
fcsonlinefcsonline
49

pr-workflow

Enforces PR-based development workflowbforking direct pushes to the main branch.

Community
Intermediate
unheadedunheaded
2

unheaded-marshal

Detect and enforce battle plan execution discipline across timelines and verification gates.

Official
Advanced
christopherlouetchristopherlouet
5

work-quick

Apply minimal code changes with syntax checks and existing tests.

Community
Basic