Principles for creating evergreen notes - atomic, lasting insights that compound over time. Use when discussing note quality, what makes a good evergreen note, or the "only what was explored" principle. Tool-agnostic concepts that apply regardless of note-taking app.
Crea planes de implementaciรณn realistas para MVPs de 2-4 semanas. Define alcance mรญnimo, stack tecnolรณgico, tareas priorizadas y cronograma. รsalo despuรฉs de validar una idea para planificar la construcciรณn del producto mรญnimo viable.
Implement plugin tasks from plan with step iteration and progress tracking
่คๆฐใฎSkillsใ้ฃๅใใใไธ้ฃใฎใฏใผใฏใใญใผใ่จญ่จใใใกใฟในใญใซใใฆใผใถใผ็ขบ่ชใใคใณใใไพๅญ้ขไฟใใจใฉใผๆใฎใใฉใผใซใใใฏใๅซใๅฎๅ จใชใฏใผใฏใใญใผๅฎ็พฉใ็ๆใ
ๆซๆ topic ็ digests Claim Ledger๏ผๆโๆชๆ ธ้ช + ๆฐๅญ้ซๅฝฑๅโๆก็ฎ่ฝฌๆ tasks๏ผๆ ธ้ชๅพ ๅ๏ผใ
HAIOS Ground Cycle for loading architectural context before cognitive work. Use before plan-authoring, investigation, or implementation cycles.
A structured framework for dynamic and reflective problem-solving through sequential thoughts. Use when tackling complex, multi-step problems that require careful analysis, revision of assumptions, or exploration of alternative approaches. Ideal for algorithm optimization, architectural decisions, debugging complex issues, or any task where initial understanding may need to evolve.
This skill MUST be used when the user asks to "link issues", "relate issues", "mark as duplicate", "blocks issue", "is blocked by", "create issue link", "connect issues", or otherwise requests creating relationships between Jira issues.
Reusable workflow patterns for skills and agents including sequential checklists, conditional routing, validation loops, and progressive disclosure. Use when designing structured procedures.
์ฒด๊ณ์ ์ธ ํ์ต ๊ณํ ์๋ฆฝ, ์คํ, ๊ฒ์ฆ์ ์ํ ํ์ต ์ ์ฉ ์ํฌํ๋ก์ฐ์ ๋๋ค. (ํจ์ฒ ํ๋๋์ ํ์ต ๋ฒ์ )
Break complex features into delegatable tasks with clear ownership and dependencies. Use for feature planning phase.
้กน็ฎ็ฅ่ฏๅบ็ฎก็ๅจ - ๅฐไฟ้ฉไธๅก้กน็ฎๆๆกฃ(ๆฐๆฎๅๆใPPTๆฅๅใๆๆฏๆนๆก)่ฝฌๅไธบ็ปๆๅใๅฏ่ฟ็งป็็ฅ่ฏ่ตไบงใๆฏๆ:(1)่ชๅจ็ๆ2็ฑปๆ ๅๅๆจกๆฟ(้กน็ฎๅฏๅจ/ๆๆฏๆนๆก);(2)ไปMarkdown/ไปฃ็ ไปๅบๆบ่ฝๆๅๆๆฏๅณ็ญๅๅฏๅค็จๆจกๅผ;(3)็ปไธๆๆกฃๆ ผๅผๆ ๅ;(4)็ๆๅฏ่ทจ้กน็ฎๅค็จ็็ฅ่ฏๅบใ่งฆๅๅบๆฏ:็จๆท่ฆๆด็้กน็ฎๆๆกฃใๅๅปบ็ฅ่ฏๅบใ็ๆ้กน็ฎๆจกๆฟใๆๅๆๆฏ็ป้ชใๆ ๅๅ็ฐๆๆๆกฃๆถไฝฟ็จใ
Automated technical debt identification, tracking, and prioritization system
ํ๋ก์ ํธ ์ํ ์ ๊ฒ ๋ฐ ๊ฑด๊ฐ ์ง๋จ. ์ํ, ์ ๊ฒ, health, check, inspect ํค์๋์ ์๋ ํ์ฑํ.
Preserves session context when context window fills. Triggers at configurable thresholds (50%/75%). Captures objective, progress, technical details, decisions, blockers, and next steps.
Detects critical product, scope, data, risk, and success ambiguities in requirements or PRDs and expresses them as structured, decision-forcing clarification questions without proposing solutions or workflow actions.
Analyze completed parallel-executor session in fresh context and generate consolidation report. Use after all parallel stages complete. Spawns isolated subagent to analyze session history and create archive document.
Weekly review process for reflection and planning. Use when: "weekly review", "week summary", "Friday review", "what happened this week".
Guide development following Kent Beck's Test-Driven Development (TDD) using Red โ Green โ Refactor cycle. Use when writing tests first, implementing features with TDD, need to write failing tests, make tests pass, refactoring after tests pass, following red-green-refactor, fixing defects with tests, or practicing test-driven development methodology.
Evening task selection ceremony for maker work (discovery: requirements-clarity). Evaluate at requirements-clarity when user mentions shutdown ritual, evening ceremony, select for book, end of day selection, or tomorrow's tasks.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
