status-map
Generate human-readable ASCII status visualizations for agent sessions
Generate human-readable ASCII status visualizations for agent sessions
Implement the next ready task from Linear issue tracker with SpecKit integration. Use when implementing tasks, working on Linear issues, or continuing feature development.
Lightweight brainstorming for personal projects. Use when someone has a rough idea they want to flesh out before coding — not for formal design docs or architecture decisions. Triggers on "I have an idea", "I want to build something", "help me think through", or when someone describes a vague project concept they want to clarify.
Enterprise Skill for advanced development
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementing features with structured TDD workflow, task tracking via todo.json, and engineering best practices.
Reflect on current session and suggest improvements to agents, commands, templates, workflows
Coordinates the 43-day Malaga Embassy sprint, managing €1,500 capital with constitutional cascade compliance (20/10/15/40/15). Tracks 3 revenue streams (Agent-as-a-Service, Intel Services, Proposal Consultation) targeting €855-1,910/month. Calculates health scores (0-100), provides spending guidance (not blocking), and activates emergency protocols when runway falls below 14 days. Use when discussing Malaga operations, embassy budget, revenue activation, or Captain BROlinni's deployment.
Bridge skill for work-type routing in CHAIN phase. Use to determine next cycle skill based on work item signals.
Create and manage epics with beads hierarchical task structure, breaking large features into manageable components
Creates Epics following the T-Minus-15 process template. Epics are large bodies of work containing multiple Features. Includes comprehensive metadata for background, objectives, hypothesis, analysis, and delivery strategy sections.
Plan development work following KB skill's structured approach with PRDs, phases, tickets, TDD specifications, and parallel execution planning. WORKFLOW: 1. KB LOOKUP - Check existing PRDs, patterns, code maps, SOPs 2. SCOPE - Small (ticket only) or Large (PRD + phases)? 3. PRD - Create for large work 4. PHASES - Break into 2-5 tickets + Phase E2E 5. TICKETS - Create with TDD spec (3-spec.md is critical) 6. PARALLEL ANALYSIS - Dependency matrix, file conflicts, execution mode 7. GIT SETUP - Phase branch, worktrees for parallel tickets 8. QUESTIONS - Resolve all ambiguity before implementation Use when: - User asks to implement something non-trivial - User says "plan", "design", "how would you implement" - Task requires multiple files or sessions - Requirements are unclear
다음 작업 계획 및 우선순위 분석. 작업, 계획, 다음, next, plan, todo 키워드에 자동 활성화.
steering skill Trigger terms: steering, project memory, codebase analysis, auto-update context, generate steering, architecture patterns, tech stack analysis, project structure, analyze codebase, understand project Use when: User requests involve steering tasks.
Use when executing implementation plans with independent tasks in the current session
Use when team reorganization planning, identifying coordination inefficiencies, validating Conway's Law, assessing team-architecture fit, or planning service splits - analyzes alignment between code module boundaries and team structures revealing organizational bottlenecks
A permanent record of identified bugs, architectural pitfalls, and logic errors. MUST be referenced before major refactors.
Enterprise Skill for advanced development