aylee
- 34 skills
- 0 followers
- 4 hours ago last updated
- ▌ Rfc 2 · ayleeWrite or revise a request for comments. Use when the user asks to propose an approach, expose tradeoffs, invite debate, or resolve an architectural direction; use decision after a choice is settled.
- ▌ Desk 2 · ayleeOrient the user across active projects, current workstreams, weekly priorities, commitments, and backburner items. Use for broad questions such as what is on the user's plate or what deserves focus; do not trigger when the user names one project to resume.
- ▌ Open 2 · ayleeOpen and orient to a project when the user names a binder, asks to resume work, or needs the current state of a known project. Load the binder and its linked workstream without rewriting “last session” history.
- ▌ Spec 2 · ayleeWrite or revise a decision-complete product specification. Use when the user asks to define the behavior, requirements, state, failure modes, or acceptance criteria for a feature or workflow; use brief for stakeholder framing rather than implementation-ready detail.
- ▌ Brief 2 · ayleeWrite or revise a concise project brief or one-pager. Use when the user asks for stakeholder alignment, a proposal, a one-page brief, or an edit to an existing brief artifact.
- ▌ Grill 2 · ayleeRelentlessly but constructively interview the user when they say “grill me,” “grill this,” or ask to stress-test a plan, design, decision, or proposal. Resolve one material decision at a time before implementation.
- ▌ Setup 2 · ayleePersonalize or upgrade an Agent-OS instance only when the user explicitly invokes setup. Preview all writes, preserve fictional examples unless removal is approved, and never overwrite global runtime or third-party skill configuration.
- ▌ Shape 2 · ayleeClarify a complex or ambiguous request before execution by establishing the real problem, outcome, audience, scope, constraints, current state, and owner. Use when acting immediately risks solving the wrong problem.
- ▌ Doctor 2 · ayleeDiagnose an Agent-OS filesystem when setup, skills, state, links, generated runtime adapters, cloud-synced files, privacy boundaries, or Gitless behavior may be unhealthy. Use for health checks and troubleshooting, not ordinary project work.
- ▌ Editor 2 · ayleeEdit an existing document when the user asks to tighten its voice, clarity, structure, formatting, or audience fit. Use for bounded document editing, not fact-free rewriting or repository-wide style changes.
- ▌ Recent 2 · ayleeFind recently active Agent-OS work when the user asks what changed or what they worked on. Prefer receipts and artifact metadata, work without Git, and use mtimes only as a fallback.
- ▌ Handoff 2 · ayleeCreate a continuation brief for a real agent, runtime, machine, parallel-lane, or context-window boundary. Use when the user clearly asks to hand work to another agent or make it resumable across a named boundary. Do not infer handoff from casual closeout or use it as a substitute for current workstream state.
- ▌ Morning 2 · ayleeProduce a concise daily briefing from current Agent-OS priorities, commitments, and workstream state. Use when the user asks for a morning brief, today's focus, or a start-of-day orientation; use desk for a fuller cross-project review.
- ▌ Closeout 2 · ayleeClose or park an explicit unit of work when the user invokes closeout. Use for deliberate state reconciliation, verification, receipts, and an optional handoff; never infer it from casual phrases such as “done” or “thanks.”
- ▌ Decision 2 · ayleeRecord a durable decision with context, options, rationale, consequences, and a future review trigger. Use when the user asks to document a choice that has actually been made; do not trigger for an unresolved question.
- ▌ Research 2 · ayleeConduct bounded research when the user asks to investigate, compare, audit, verify, or recommend based on evidence. Search local context first, use current primary sources when needed, and separate fact from inference.
- ▌ Weekly Review 2 · ayleeRun the deliberate weekly review ritual when the user explicitly invokes it. Persist a durable review, reconcile priorities and commitments, and preserve history without depending on Git or deleting source records.
- ▌ Rfc · aylee bundleWrite or revise a request for comments. Use when the user asks to propose an approach, expose tradeoffs, invite debate, or resolve an architectural direction; use decision after a choice is settled.
- ▌ Desk · aylee bundleOrient the user across active projects, current workstreams, weekly priorities, commitments, and backburner items. Use for broad questions such as what is on the user's plate or what deserves focus; do not trigger when the user names one project to resume.
- ▌ Open · aylee bundleOpen and orient to a project when the user names a binder, asks to resume work, or needs the current state of a known project. Load the binder and its linked workstream without rewriting “last session” history.
- ▌ Spec · aylee bundleWrite or revise a decision-complete product specification. Use when the user asks to define the behavior, requirements, state, failure modes, or acceptance criteria for a feature or workflow; use brief for stakeholder framing rather than implementation-ready detail.
- ▌ Brief · aylee bundleWrite or revise a concise project brief or one-pager. Use when the user asks for stakeholder alignment, a proposal, a one-page brief, or an edit to an existing brief artifact.
- ▌ Grill · aylee bundleRelentlessly but constructively interview the user when they say “grill me,” “grill this,” or ask to stress-test a plan, design, decision, or proposal. Resolve one material decision at a time before implementation.
- ▌ Setup · aylee bundlePersonalize or upgrade an Agent-OS instance only when the user explicitly invokes setup. Preview all writes, preserve fictional examples unless removal is approved, and never overwrite global runtime or third-party skill configuration.
- ▌ Shape · aylee bundleClarify a complex or ambiguous request before execution by establishing the real problem, outcome, audience, scope, constraints, current state, and owner. Use when acting immediately risks solving the wrong problem.
- ▌ Doctor · aylee bundleDiagnose an Agent-OS filesystem when setup, skills, state, links, generated runtime adapters, cloud-synced files, privacy boundaries, or Gitless behavior may be unhealthy. Use for health checks and troubleshooting, not ordinary project work.
- ▌ Editor · aylee bundleEdit an existing document when the user asks to tighten its voice, clarity, structure, formatting, or audience fit. Use for bounded document editing, not fact-free rewriting or repository-wide style changes.
- ▌ Recent · aylee bundleFind recently active Agent-OS work when the user asks what changed or what they worked on. Prefer receipts and artifact metadata, work without Git, and use mtimes only as a fallback.
- ▌ Handoff · aylee bundleCreate a continuation brief for a real agent, runtime, machine, parallel-lane, or context-window boundary. Use when the user clearly asks to hand work to another agent or make it resumable across a named boundary. Do not infer handoff from casual closeout or use it as a substitute for current workstream state.
- ▌ Morning · aylee bundleProduce a concise daily briefing from current Agent-OS priorities, commitments, and workstream state. Use when the user asks for a morning brief, today's focus, or a start-of-day orientation; use desk for a fuller cross-project review.
- ▌ Closeout · aylee bundleClose or park an explicit unit of work when the user invokes closeout. Use for deliberate state reconciliation, verification, receipts, and an optional handoff; never infer it from casual phrases such as “done” or “thanks.”
- ▌ Decision · aylee bundleRecord a durable decision with context, options, rationale, consequences, and a future review trigger. Use when the user asks to document a choice that has actually been made; do not trigger for an unresolved question.
- ▌ Research · aylee bundleConduct bounded research when the user asks to investigate, compare, audit, verify, or recommend based on evidence. Search local context first, use current primary sources when needed, and separate fact from inference.
- ▌ Weekly Review · aylee bundleRun the deliberate weekly review ritual when the user explicitly invokes it. Persist a durable review, reconcile priorities and commitments, and preserve history without depending on Git or deleting source records.