Draft quick specs and run compressed TDD cycles for small isolated changes.
npx skills add https://github.com/yabafre/aped-claude --skill aped-quick
Please help me install this Agent Skill. Skill: aped-quick Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-quick Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-quick
APED-quick helps you complete small, isolated changes (like hotfixes or minor refactors) without running the full A→P→E→D→R pipeline, while still enforcing a disciplined spec-first workflow and explicit user validation.
Tell the APED agent to run aped-quick to make a quick fix by answering what needs to change, why it matters now, and whether it is a fix, feature, or refactor.
High-intent search queries and answers about installing and using this skill.
Ship a quick hotfix by bypassing the full pipeline and using a quick-spec gate to draft, track, and approve small isolated changes within a single session. This fast-track approach enforces a compressed TDD loop and requires explicit user validation before implementation begins.
A quick spec is a time-boxed file that drafts the scope of minor changes, tracking lifecycle from draft to done or abandoned. It requires user approval before implementation, ensuring disciplined delivery of small refactors or features.
Use a quick spec instead of a full TDD workflow when your change fits within five or fewer files, can be finished in one session, and requires no new dependencies or architectural pattern changes. It is designed for hotfixes, quick features, and minor refactors.
No, this fast-track TDD workflow explicitly prevents changes that introduce new dependencies or new architectural patterns. Guardrails enforce that work stays within quick-mode constraints to maintain scope and prevent bypassing the enabled state.
Integrate quick fixes by labeling work appropriately through your ticket system and git provider, then following guided PR creation patterns. The workflow ensures your isolated changes are tracked from the quick-spec draft through to the final pull request.
Yes, aped-quick runs a compressed TDD loop consisting of RED, GREEN, and REFACTOR phases to ensure minimal implementation satisfies acceptance criteria. This enforces test-driven development for your isolated changes before user approval.
mhdxbilalDiagnose environment health across Octopus components and report remediation steps.
timsvoiceSquash commits and create a pull request via gh for code review.
ed3daiplaceholder
qa-amanDefine penetration testing engagement scope with targets, objectives, and authorization.
