All authors

Claude Skills by shakestzd
github.com/shakestzd33 skills0 installs1 views
- Memory Sync SkillUse this skill for documentation synchronization and memory file management. **Trigger keywords:** sync, documentation, memory, AGENTS.md, CLAUDE.md, GEMINI.md, sync-docs ---Votes: 0GitHub stars: 4
- Parallel OrchestratorOrchestrate parallel agent workflows using Wipnote's ParallelWorkflow. Activate when planning multi-agent work, using Task tool for sub-agents, or coordinating concurrent feature implementation.Votes: 0GitHub stars: 4
- Debugging Workflow SkillUse this skill for systematic debugging with research-first approach. **Trigger keywords:** debug, error, bug, troubleshoot, investigate, research, fix ---Votes: 0GitHub stars: 4
- Deployment Automation SkillUse this skill for deployment, versioning, and release workflows in the Wipnote project. **Trigger keywords:** deployment, release, publish, version, pypi, package, build, distribute ---Votes: 0GitHub stars: 4
- Wipnote Dogfooding SkillUse this skill to understand how Wipnote dogfoods itself and learn from real examples. **Trigger keywords:** dogfooding, examples, learn, patterns, real usage, wipnote development, self-tracking ---Votes: 0GitHub stars: 4
- Parallel OrchestratorARCHIVED — Use orchestrator-directives-skill instead. Orchestrate parallel agent workflows using Task tool. Activate when planning multi-agent work or coordinating concurrent feature implementation.Votes: 0GitHub stars: 4
- Wipnote TrackerARCHIVED — Use wipnote skill instead. wipnote workflow combining session tracking, orchestration, and parallel coordination.Votes: 0GitHub stars: 4
- Agent ContextRules shared by wipnote agents: work attribution, safety rules, research routing, truncation-resilient reporting. Preloaded into coder agents via skills:.Votes: 0GitHub stars: 4
- Arch BootstrapBootstrap architectural memory for a repo — generates starter cards from a structured briefVotes: 0GitHub stars: 4
- Code Quality SkillCode hygiene, quality gates, and pre-commit workflows. Use for linting, type checking, testing, and fixing errors. Works for Go, JavaScript/TypeScript, Python, Rust, and any other language.Votes: 0GitHub stars: 4
- DeployDeploy and release wipnote — run quality gates, bump version, tag, push, and trigger GitHub release pipeline. Use when asked to deploy, release, publish, ship, or push a new version.Votes: 0GitHub stars: 4
- DiagnoseDiagnose bugs, errors, and issues with root cause analysis. Use when asked to diagnose, debug, investigate, or find root cause of any problem — whether a wipnote bug ID, error message, unexpected behavior, or delegation audit.Votes: 0GitHub stars: 4
- ExecuteExecute a parallel plan using dependency-driven dispatch. Checks file overlap among unblocked tasks, partitions into non-conflicting waves, and dispatches simultaneously. Merges completed work, then dispatches newly unblocked tasks. No manual wave sequencing.Votes: 0GitHub stars: 4
- Guard AuthoringAuthor, approve, and maintain project guard profiles (.wipnote/guard-profile.yaml). Use for custom quality/completion/yolo gates, polyglot monorepo per-directory guards, re-approving after drift, and understanding the trust boundary and autodetection fallback.Votes: 0GitHub stars: 4
- Orchestrator Directives SkillDecision rules for acting as the wipnote orchestrator: choosing which agent or external CLI gets a task, writing a subagent brief, dispatching in parallel, recovering a stalled or budget-paused agent, and completing work that a subagent implemented. Not needed for hands-on coding done directly in a non-orchestrator session.Votes: 0GitHub stars: 4
- Plan CritiqueDual-critic review pass for a drafted plan. Runs DESIGN CRITIC and FEASIBILITY CRITIC agents in parallel against the plan YAML, then writes findings as critic_revisions on the affected slices. Use when asked to critique this plan, review plan, run plan critic pass, or before human review of a multi-slice plan.Votes: 0GitHub stars: 4
- PlanPlan development work using a triage-gated, blocks-first interview. Classify scope as trivial/standard/complex, then run 0/3/4 staged interview rounds through the current harness native ask-user tool when available, or plain conversation when it is not. Each stage elicits the VISUAL block first (file-tree, data-model, wireframe/diagram) and derives the prose slice fields (what/why/done_when) from it — blocks are authored inline as the YAML is built, not in a post-pass. Produces slice-card YAM...Votes: 0GitHub stars: 4
- Report IssueReport a wipnote bug or issue to the development team from any supported harness. Use when the user asks to report an issue, file a bug, or says the report-issue slash command is unavailable.Votes: 0GitHub stars: 4
- Spec From SliceElicit Scope/Decisions/Context for a plan slice and generate its OpenSpec-formatted feature spec. Use after a slice is approved but before promote-slice, or any time a slice needs decisions captured. Wraps the cross-harness `wipnote plan elicit-decisions` CLI plus `wipnote spec generate --insert`.Votes: 0GitHub stars: 4
- Strategic PlanningUse wipnote analytics to make smart work prioritization decisions. Activate when recommending work, finding bottlenecks, assessing risks, or analyzing project impact.Votes: 0GitHub stars: 4
- Tdd ProtocolTDD protocol for sub-agent implementation tasks — write failing tests first, run quality gates, commit format, attribution rulesVotes: 0GitHub stars: 4
- Ui Stills VerificationStills-based UI verification — probe the DOM, capture ONE component with shot-scraper, READ the PNG back with the image tool, judge. Use whenever a task touches web UI (templates, CSS, dashboard, LiveView, React, any rendered page) and before claiming UI work is done; also the researcher's default visual-QA method when no browser MCP is available. Headless, needs no extension or browser session.Votes: 0GitHub stars: 4
- Visual PlanSECONDARY enrichment path — add or revise structured visual blocks (data-model, file-tree, wireframe, diagram, tabs) on an EXISTING wipnote plan. Use for legacy plans drafted before blocks-first existed, or for ad-hoc later block additions/revisions — NOT for primary planning. New plans get blocks authored inline during the wipnote:plan interview (blocks-first); only reach for this skill when a plan already exists and needs blocks added or changed after the fact. Reads the live block catalog ...Votes: 0GitHub stars: 4
- Visual RecapGenerate a grounded visual recap for a work item, git range, or session. Runs wipnote recap to produce a self-contained HTML artifact grounded in the real diff, reads the artifact, writes an outcome narrative (secrets redacted), and links to the dashboard recap URL. Use when asked to recap, summarize, or visualize completed work.Votes: 0GitHub stars: 4
- Parallel OrchestratorARCHIVED — Use orchestrator-directives-skill instead. Orchestrate parallel agent workflows using Task tool. Activate when planning multi-agent work or coordinating concurrent feature implementation.Votes: 0GitHub stars: 4
- Wipnote TrackerARCHIVED — Use wipnote skill instead. wipnote workflow combining session tracking, orchestration, and parallel coordination.Votes: 0GitHub stars: 4
- DiagnoseDiagnose bugs, errors, and issues with root cause analysis. Use when asked to diagnose, debug, investigate, or find root cause of any problem — whether a wipnote bug ID, error message, unexpected behavior, or delegation audit.Votes: 0GitHub stars: 4
- ExecuteExecute a parallel plan using dependency-driven dispatch. Checks file overlap among unblocked tasks, partitions into non-conflicting waves, and dispatches simultaneously. Merges completed work, then dispatches newly unblocked tasks. No manual wave sequencing.Votes: 0GitHub stars: 4
- Orchestrator Directives SkillDecision rules for acting as the wipnote orchestrator: choosing which agent or external CLI gets a task, writing a subagent brief, dispatching in parallel, recovering a stalled or budget-paused agent, and completing work that a subagent implemented. Not needed for hands-on coding done directly in a non-orchestrator session.Votes: 0GitHub stars: 4
- Parallel OrchestratorARCHIVED — Use orchestrator-directives-skill instead. Orchestrate parallel agent workflows using Task tool. Activate when planning multi-agent work or coordinating concurrent feature implementation.Votes: 0GitHub stars: 4
- DiagnoseDiagnose bugs, errors, and issues with root cause analysis. Use when asked to diagnose, debug, investigate, or find root cause of any problem — whether a wipnote bug ID, error message, unexpected behavior, or delegation audit.Votes: 0GitHub stars: 4
- ExecuteExecute a parallel plan using dependency-driven dispatch. Coordinate ready work items, partition non-conflicting slices, and keep all spawned agents attributed and closed.Votes: 0GitHub stars: 4
- Orchestrator Directives SkillDecision rules for acting as the wipnote orchestrator: choosing which agent or external CLI gets a task, writing a subagent brief, dispatching in parallel, recovering a stalled or budget-paused agent, and completing work that a subagent implemented. Not needed for hands-on coding done directly in a non-orchestrator session.Votes: 0GitHub stars: 4