skills.rest
runbear-io
runbear-ioOFFICIAL
Explore all skills by this author →
Website𝕏@runbear_ioGitHub

hire

Create aweek subagent manifests and plan.md files via guided interview.

11|1|Updated Apr 20, 2026
Search Tags:#workflow#planning#agent#subagent#plan.md#hire#aweek
One-click install
npx skills add https://github.com/runbear-io/aweek --skill hire-runbear-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hire
Source: https://github.com/runbear-io/aweek/tree/main/skills/hire
Command: npx skills add https://github.com/runbear-io/aweek --skill hire-runbear-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hire (create) a new aweek agent by collecting identity details and conducting a short interview to author a ready-to-use plan.md, enabling immediate plan-ready onboarding.

Core Features & Use Cases

  • Create a minimal subagent.md in .claude/agents and a corresponding aweek scheduling shell.
  • Conduct an interview to populate long-term goals, monthly plans, strategies, and notes into plan.md.
  • Validate inputs, handle both creating new and adopting existing subagents, and persist artifacts in a single workflow.

Quick Start

Run the interactive hire flow to create a new subagent and generate its plan.md.

Frequently Asked Questions about hire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a new subagent and generate its plan.md?▼

Onboard a new subagent by running an interactive interview flow that collects identity details, creates a subagent manifest, and writes a ready-to-use plan.md for immediate scheduling.

What is the best way to create an aweek agent from an existing subagent?▼

Create an aweek agent from an existing subagent by choosing the adoption flow, which validates the existing identity details and generates a matching scheduling shell without overwriting prior configurations.

Where are subagent metadata and scheduling shells stored during the hire workflow?▼

Subagent metadata and scheduling shells are stored under the .claude/agents directory and the .aweek directory, persisting both the manifest and the generated plan.md artifacts.

Does the hire flow require guided input to populate long-term goals and monthly plans?▼

Yes, the hire flow requires a guided interview to populate long-term goals, monthly plans, strategies, and notes into the plan.md file, ensuring the subagent is plan-ready.

Can I validate subagent identity details before writing the manifest and plan?▼

The workflow validates all identity details during the interview phase, ensuring inputs are correct before writing the subagent metadata and the initial scheduling shell.

What happens if subagent onboarding fails to write files to the .aweek directory?▼

Onboarding requires write access to the .aweek and .claude directories; without it, the workflow cannot persist the scheduling shell or subagent manifest and will fail to complete.

Related Skills

Explore More Product & Management Skills→
runbear-iorunbear-io
11

teardown

Remove aweek heartbeat and .aweek/ data directory with confirmations.

Official
Advanced
ballredballred
1.7k

goal-tracking

Cascade three-year visions into yearly, monthly, and weekly goals with progress tracking.

Community
Intermediate
runbear-iorunbear-io
11

plan

Edit agent plan.md files and manage weekly task approvals.

Official
Advanced
runbear-iorunbear-io
11

config

Inspect and update aweek configuration in .aweek/config.json with validation.

Official
Advanced