skill-developer

Automate skill creation by following the phase-based framework: use planning templates for Phase 1 design decisions, implementation templates for Phase 2 build steps, and validation checklists for Phase 3 quality gates. This standardizes skill structure, configuration, and auto-activation triggers across universal, domain-specific, and guardrail types.

Apply the three-phase methodology: Phase 1 defines design decisions and functional requirements; Phase 2 implements main skill content and progressively loaded resources; Phase 3 validates against mandatory checklists. Configure skill-rules.json, enforce directive-language requirements, and respect token-budget constraints for scalable, reliable deployments.

Yes, skill development uses Markdown for documentation and YAML for configuration files. These dependencies are built into the skill-creation framework to standardize documentation structure and skill-rules.json formatting across deployments.

Configure auto-activation triggers in Phase 2 implementation by defining explicitly when your skill loads and activates. The framework enforces clear trigger definitions in skill-rules.json and ensures progressive resource loading follows activation rules for efficient, controlled deployment.

Phase 3 validation requires completing mandatory task decomposition rules, token-budget constraint verification, skill-rules.json compliance, and directive-language enforcement checks. The quality checklist ensures all functional requirements are met before deployment.

Yes, the framework applies uniformly across universal, domain-specific, and guardrail skill types. Each type follows the same phase-based planning, implementation, and validation process with type-specific functional requirements enforced through the skill-rules.json configuration.