aiskillstore/planning
skills/doyajin174/planning/SKILL.md
Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 4:10 PM54.8s2 files scanned
SKILL.md
- name:
- planning
- description:
- Transform ideas into actionable implementation plans. Combines Socratic questioning for requirements discovery with detailed task breakdown for zero-context engineers. Use before any feature development.
- allowed-tools:
- Read, Glob, Grep, Edit, Write, AskUserQuestion
- license:
- MIT
- author:
- obra/superpowers
- version:
- 2.0
Planning
아이디어를 구체적인 구현 계획으로 발전시키는 통합 스킬입니다.
Phase 1: Discovery (Brainstorming)
Socratic Process
1. 핵심 목표 파악
- "이것이 해결하려는 문제가 무엇인가요?"
- "성공을 어떻게 측정할 수 있나요?"
2. 제약 조건 탐색
- "반드시 지켜야 할 제약이 있나요?"
- "기술적/비즈니스적 한계는?"
3. 대안 탐색
- 최소 3가지 접근법 도출
- 각 접근법의 장단점 분석
Output: Discovery Summary
## Discovery Summary
### 핵심 요구사항
- [필수 요구사항 목록]
### 기술적 결정사항
- [합의된 접근법]
### 열린 질문
- [추가 탐색 필요 항목]
Phase 2: Plan Writing
Core Principle
"가정: 엔지니어가 코드베이스 컨텍스트가 전혀 없음"
Plan Structure
# [Feature Name] Implementation Plan
## Goal
[한 문장 목표]
## Tech Stack
- Framework: [프레임워크]
- Dependencies: [의존성]
## File Structure
[영향받는 파일 목록]
Bite-sized Tasks (각 2-5분)
## Task 1: [태스크명]
### Files
- `src/feature/file.ts` (신규/수정)
### Test First
[테스트 코드]
### Implementation
[구현 코드]
### Commit
```bash
git commit -m "feat(scope): description"
---
## Workflow
Discovery → Plan → Execute
┌────────────────┐ │ Brainstorm │ ← 요구사항 도출 └───────┬────────┘ ▼ ┌────────────────┐ │ Write Plan │ ← 태스크 분해 └───────┬────────┘ ▼ ┌────────────────┐ │ Execute │ ← TDD 사이클 └────────────────┘
## Plan Storage
docs/plans/YYYY-MM-DD-<feature-name>.md
## Checklist
### Discovery 완료
- [ ] 핵심 목표 명확
- [ ] 제약 조건 파악
- [ ] 접근법 결정
### Plan 완료
- [ ] 모든 파일 경로 정확
- [ ] 각 태스크 2-5분 분량
- [ ] 테스트 코드 포함
- [ ] 커밋 메시지 작성됨
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026