create-plan
Create Implementation Plan
Instructions
Create a detailed, high-quality implementation plan as a ticket (tagged plan) that adheres to strict quality standards and provides complete guidance for implementation.
Phase 1: Understanding & Validation
Step 0: Extract Original Issue/Task Requirements (MANDATORY)
CRITICAL: Before creating any plan, extract ALL requirements from the original issue/task.
# GitHub:
gh issue view <number>
# Forgejo:
tea issue view <number> # or Forgejo API
More from cygnusfear/agent-skills
file-name-wizard
Audit all filename and naming conventions in the codebase against AGENTS.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
1.2Karchitectural-analysis
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health.
34video-explorer
This skill should be used when analyzing video files. You cannot process video directly, so this skill extracts frames hierarchically - starting with a quick overview, then zooming into regions of interest with higher resolution and temporal density. Use when asked to watch, analyze, review, or understand video content.
34review-changes
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
33design-spec-extraction
Use when extracting design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant JSON with component trees for code generation and developer handoff.
32obsidian-plan-wiki
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
31