strelov1
- 20 skills
- 0 followers
- 5 hours ago last updated
- ▌ Brainstorming · strelov1 bundle[Superpowers 6.2.0, MIT] You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- ▌ Using Git Worktrees · strelov1[Superpowers 6.2.0, MIT] Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
- ▌ Test Driven Development · strelov1 bundle[Superpowers 6.2.0, MIT] Use when implementing any feature or bugfix, before writing implementation code
- ▌ Verification Before Completion · strelov1[Superpowers 6.2.0, MIT] Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- ▌ Using Freehire · strelov1Use when orienting in the `freehire` CLI as a whole — installing it, authenticating with an API key, working out which of its surfaces answers a job seeker's question, or troubleshooting a 401. The task skills do the work; this one is the map and the setup.
- ▌
- ▌ Freehire Job Search · strelov1Use when finding IT jobs for someone — searching or filtering the freehire catalogue by keyword, region, seniority, skills, salary or company; reading a posting or a company's open roles; discovering what values a filter accepts; reading the saved job-search profile before asking someone what they want; handing over a job link freehire does not carry yet; or reading the "possibly inactive" signal on a posting. Covers profile, facets, search, job, company and contribute, all with machine-readable `--json` output.
- ▌ Freehire Market Fit · strelov1Use when measuring a set of skills — a CV's stack, or one skill on its own — against live open-vacancy demand on freehire; when telling a candidate which in-demand skills they are missing and what learning each would unlock; or when gauging how much of a filtered market (a role, a region, a seniority) their current stack already covers.
- ▌ Freehire Mail Triage · strelov1Use when sorting a job seeker's application mail into the freehire tracker from their own mail client (himalaya, mbsync, notmuch, the Gmail API, any IMAP) — pushing a fetched batch, judging what each message is, linking it to an application, advancing a stage from a reply, or draining the two queues the matcher fills (suggested links awaiting a verdict, and mail with no application to attach to).
- ▌ Freehire Track Applications · strelov1Use when recording or reviewing what someone applied to on freehire — marking a job applied, bookmarking one for later, moving an application through its stages (applied through offer, or rejected/withdrawn), attaching a note, or listing what they are tracking. Also covers reporting a posting that never answered them after they applied (`ghost report`), and retracting that report.
- ▌ Spike · strelov1Use before planning a risky change - a throwaway feasibility experiment that answers "is this even possible?" cheaply and ends in a VALIDATED / PARTIAL / INVALIDATED verdict
- ▌ Simplify · strelov1Use after tests pass and before code review - a portable quality pass that simplifies recently changed code while preserving behavior
- ▌ Spec Driven Tdd · strelov1The spec-driven-tdd delivery workflow (orchestrator) - runs the full lifecycle for an OpenSpec change: OpenSpec planning/tracking + Superpowers TDD, simplify, and code review. Invoked by using-spec-driven-tdd; run it once implementation starts
- ▌ Systematic Debugging · strelov1 bundle[Superpowers 6.2.0, MIT] Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- ▌ Receiving Code Review · strelov1[Superpowers 6.2.0, MIT] Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- ▌ Using Spec Driven Tdd · strelov1Entry point for the spec-driven-tdd workflow - invoke at the START of an OpenSpec change to load the delivery discipline and hand off to the spec-driven-tdd orchestrator before writing code
- ▌ Requesting Code Review · strelov1 bundle[Superpowers 6.2.0, MIT] Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- ▌ Dispatching Parallel Agents · strelov1[Superpowers 6.2.0, MIT] Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- ▌ Subagent Driven Development · strelov1 bundle[Superpowers 6.2.0, MIT] Use when executing implementation plans with independent tasks in the current session
- ▌ Finishing A Development Branch · strelov1[Superpowers 6.2.0, MIT] Use when implementation is complete, all tests pass, and you need to decide how to integrate the work