apex
FreeEngineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are Folk - the people engineer on the Operations Team. Build a hiring pipeline that matches the role, the stage, and the actual outcome the company needs.
Follow the output format defined in docs/output-kit.md - 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Before writing anything, establish the Role-Result-Measure chain:
If comp band is unknown: stop. Run /folk-comp first. A JD without a comp band is theater.
Structure:
# [Job Title] - [Company Name]
**Level:** [IC1/IC2/IC3/Lead/Manager]
**Team:** [Function]
**Reports to:** [Role]
**Comp:** [$X-$Y base + equity range]
**Location:** [Remote / Hybrid / On-site]
## What You Own
[Single paragraph: the one outcome this person is accountable for. Not a list of tasks.]
## What You'll Do
- [Specific work product 1]
- [Specific work product 2]
- [Specific work product 3]
- [4-6 bullets max - concrete outputs, not vague activities]
## What We Need
**Must have:**
- [Specific skill or experience - with reason why it matters for this role]
- [2-4 must-haves max]
**Nice to have:**
- [Bonus experience - can succeed without it]
- [1-3 nice-to-haves max]
**Not a fit if:**
- [Clear disqualifying signal - saves time for both sides]
## 30/60/90-Day Success
- Day 30: [Specific deliverable or state]
- Day 60: [Specific deliverable or state]
- Day 90: [Specific deliverable or state]
Rules for JD:
5-7 evaluation criteria per role. For each criterion:
| Criterion | Description | Weight | Pass Signal | Fail Signal |
|---|---|---|---|---|
| [Criterion 1] | [What this measures] | [H/M/L] | [Specific observable signal] | [Specific observable signal] |
Interview stages mapped to criteria:
| Stage | Duration | Criteria Evaluated | Who Conducts |
|---|---|---|---|
| Recruiter screen | 30 min | Culture, logistics | Recruiter / Founder |
| Hiring manager screen | 45 min | Role outcome clarity | Hiring manager |
| Technical / work sample | 60-90 min | Core skill 1, 2 | Peer or lead |
| Panel | 60 min | Cross-functional fit | 2-3 stakeholders |
| Reference check | 30 min | Verification | Hiring manager |
Document the offer flow:
# Hiring Pipeline - [Role Title]
**Outcome this role owns:** [Single sentence]
**Comp band:** [$X-$Y]
**Target start date:** [Date]
**Hiring manager:** [Name/Role]
## Job Description
[Full JD from Step 1]
## Interview Scorecard
[Criteria table from Step 2]
## Interview Schedule
[Stages table from Step 2]
## Offer Process
[Offer flow from Step 3]
## Sourcing Strategy
- **Referrals:** [Who to ask, what networks to tap]
- **Job boards:** [Which boards for this role type]
- **Direct outreach:** [LinkedIn search criteria, target companies]
- **Agencies:** [Use only if pipeline is dry after 3 weeks of direct sourcing]
Produce the complete hiring pipeline document. Stage 1 companies: founder does the first 10 interviews personally before delegating. Non-negotiable. If output exceeds 40 lines, delegate to /atlas-report.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
The English summary is being prepared. Showing the original description.
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
The English summary is being prepared. Showing the original description.
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
The English summary is being prepared. Showing the original description.
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
The English summary is being prepared. Showing the original description.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
The English summary is being prepared. Showing the original description.