f5-core
Scannednpx machina-cli add skill Fujigo-Software/f5-framework-claude/_core --openclawFiles (1)
SKILL.md
1.8 KB
F5 Framework Core Skills
This skill provides the foundational knowledge for F5 Framework:
Contents
- Workflow - F5 development workflow phases
- Quality Gates - D1-D4 and G1-G4 gate definitions
- Behavioral Modes - strict, standard, exploratory
Auto-load
These skills are automatically loaded when F5 Framework is active.
Quick Reference
Workflow Phases
- D1: Research Complete - Market/tech research, stakeholder interviews
- D2: SRS Approved - Software Requirements Specification
- D3: Basic Design Approved - System architecture, data model
- D4: Detail Design Approved - Module design, API contracts
- G2: Implementation Ready - Code complete, unit tests
- G2.5: Verification Complete - Asset verification, visual QA
- G3: Testing Complete - All tests pass, security scan
- G4: Deployment Ready - Staging verified, UAT approved
Behavioral Modes
- coding: Code-first, minimal explanations, production-ready
- analytical: Systematic analysis, data-driven decisions
- security: Paranoid mode, OWASP checks, defense in depth
- debugging: Root cause analysis, systematic diagnosis
- review: Constructive feedback, best practices check
- planning: Strategic thinking, phased approach
- teaching: Step-by-step explanations, examples
- performance: Metrics-driven optimization
- creative: Innovative approaches, exploration
Gate Commands
/f5-gate check D1 # Check gate D1
/f5-gate check G2 # Check gate G2
/f5-gate status # Show all gates status
$ARGUMENTS
Source
git clone https://github.com/Fujigo-Software/f5-framework-claude/blob/main/plugins/f5-core/skills/_core/SKILL.mdView on GitHub Overview
F5-core provides the foundational workflow for the F5 Framework, including the D1-D4 and G1-G4 quality gates and the Behavioral Modes. It standardizes development from research through deployment and ties checks to gate definitions.
How This Skill Works
It maps workflow phases from D1 to G4, defines gate commands for verification, and enables auto-load to be active when the framework runs. You switch Behavioral Modes such as coding, analytical, security, debugging, and more to match the current task, guided by gate status and QA criteria.
When to Use It
- Kick off a new F5 project and align on D1-D4 research and design milestones
- Prepare for implementation and unit tests at G2 to ensure readiness
- Conduct verification and visual QA at G2.5 to confirm asset quality
- Perform deployment readiness review with G4 and UAT approval
- Switch to security or debugging mode during issue diagnosis and root-cause analysis
Quick Start
- Step 1: Review the Quick Reference for Workflow Phases and Behavioral Modes
- Step 2: Use gate commands like /f5-gate check D1 and /f5-gate status to verify progress
- Step 3: Set the Behavioral Mode to coding or security as needed and align with current gates
Best Practices
- Map every gate to concrete acceptance criteria (D1-D4, G1-G4)
- Run gate checks with /f5-gate check and monitor /f5-gate status regularly
- Choose Behavioral Mode appropriate for the task and document the rationale
- Keep auto-load enabled so F5 Framework context stays active
- Integrate gate status into your planning and review cadence
Example Use Cases
- A team begins with D1 research and stakeholder interviews to shape requirements
- D2 SRS approval is obtained, followed by D3 Basic Design approval for architecture decisions
- G2 is reached as code is ready with unit tests and implementation readiness
- G2.5 confirms asset verification and visual QA before proceeding
- G4 deployment readiness is established with staging verification and UAT approval
Frequently Asked Questions
Add this skill to your agents
