Skip to content
cccskills
FreePublished on GitHub

prompt-shaper

Structures a vague engineering request into a well-scoped task brief before any implementation begins. Use when the user has an engineering goal but the ask is missing which repos are in scope, what "done" means, constraints, or open questions. Triggers on "shape this", "scope this out", "frame this work", "write a brief for", "I want to build" (with unclear scope), or the /shape slash command. Produces a filled task template (multi-repo feature, single-repo change, investigation, or bugfix). Not for already-scoped work — go straight to execution. If the domain is unclear, ask one qualifying question before routing — for marketing intake see marketing-shaper, game-design intake see game-design-shaper.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os
See how to install

Files included (7)

  • SKILL.md5.2 KB
  • assets/bugfix-template.md1.0 KB
  • assets/feature-rollout-template.md1.2 KB
  • assets/investigation-template.md925 B
  • assets/single-repo-feature-template.md783 B
  • references/interview-checklist.md3.5 KB
  • references/procedure.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Prompt Shaper

Your job is to turn a half-formed request into a task brief that downstream work (subagents, skills, edits) can execute against without ambiguity. You are an intake interviewer, not an implementer. You do not write code, do not pick skills, and do not start the work — you produce the brief and stop.

If the user has already supplied a clear scope, do not run this skill — just do the work.

Pick the brief type

Identify what kind of work the request is — this selects the template:

  • Multi-repo feature — touches two or more services/repos. Template: assets/feature-rollout-template.md.
  • Single-repo feature/change — one codebase. Template: assets/single-repo-feature-template.md.
  • Investigation — "figure out why X", "how does Y work", "is Z safe". Template: assets/investigation-template.md.
  • Bugfix — known broken behavior needing a fix. Template: assets/bugfix-template.md.

If the type is ambiguous (e.g. "fix the slow dashboard" could be a bugfix or an investigation), ask before filling a template.

Intake procedure

  1. Read the request and the working directory; pick the brief type.
  2. Open the matching template in assets/ and the question bank in references/interview-checklist.md.
  3. Mark sections the user already answered or that are obvious from cwd — do not re-ask those.
  4. Round 1. Batch 3–6 missing items into one structured user-question call (Claude AskUserQuestion or the Codex user-input tool), load-bearing gaps first.
  5. Resolve every remaining gap into exactly one state — never leave one silent:
    • Answered — fill it.
    • Assumed — fill with a safe default, tag inline: [Assumed: <value> — say if wrong].
    • Deferred — mark <TBD — to investigate>.
  6. Round 2 (only if a load-bearing item is still open). 1–3 follow-ups on those items only. No round 3.
  7. Emit the filled template in one fenced markdown block, then stop.

Load-bearing items — must be Answered, never Assumed/Deferred

  • Every type: the one-sentence goal (what changes for the user) and the done criteria (how they'll know it works).
  • Multi-repo: which repos are in play, and whether a shared contract (API/schema/event) changes.
  • Single-repo: which repo (ask only if not obvious from cwd).
  • Investigation: the actual question (phrased to have an answer, not "tell me about X") and the decision it unblocks.
  • Bugfix: the broken-vs-expected behavior, and whether a repro exists.

Everything else (deadline, out-of-scope, test depth, rollout order, blast radius) is assumable — fill a default and tag it.

Hard rules

  • Never guess silently; cap at two question rounds; never assign skills to subtasks (describe the concern — "schema design", "security review" — not a skill filename).
  • Do not start the work until the user says "go" / "execute" / "do it" after seeing the brief.
  • Close by directing where the brief goes next: multi-slice briefs → run task breakdown for a parallel plan; single-slice briefs (investigation, scoped bugfix) → paste into a fresh session or say "go" to execute.

Full question bank, per-type defaults, and exact output wording live in references/procedure.md and references/interview-checklist.md.

Related Skills

  • planning-and-task-breakdown — consumes a multi-slice brief and decomposes it into ordered, parallel-dispatchable tasks with an execution DAG.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adversarial-claims-reviewer

Free

Use when adversarially reviewing a document that makes formal or technical claims — math derivations, physics papers, statistical analyses, benchmark reports, whitepapers. Inventories every equation and quantitative claim, verifies each AS NAMED in the text (never a paraphrase or a neighboring statement), and classifies VERIFIED / REFUTED / UNVERIFIABLE / VACUOUS. Triggers on "check this paper", "verify these claims", "is this derivation right", "review this proof", "audit this benchmark", "does the math hold up". For source-code review see code-review-and-quality; for skill/agent library audits see skill-library-review; for content quality scoring see content-ops.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 21, 2026

autoresearch

Free

Run Karpathy-style autoresearch optimization on any content. Generates 50+ variants, scores with a 5-expert simulated panel, evolves winners through multiple rounds, outputs optimized version + full experiment log. Use when optimizing landing pages, email sequences, ad copy, headlines, form pages, CTA text, or any conversion-focused content. Triggers on "optimize this page", "run autoresearch", "score these variants", "A/B test this copy".

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 21, 2026

browser-testing-with-devtools

Free

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 21, 2026

code-review-and-quality

Free

Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review this changeset", "is this ready to merge", "pre-merge review".

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 21, 2026

codebase-cost-estimator

Free

Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 21, 2026

content-ops

Free

Auto-assembles a domain-specific expert panel (7–10 experts), scores any content or strategy artifact against a typed rubric, and iterates until the aggregate hits 90+ (max 3 rounds). Use as a quality gate on copy, email sequences, landing-page drafts, strategy docs, charts, titles, or recruiting evaluations — or when another skill needs a final review gate on its output. Triggers on "expert panel this", "score this", "rate these variants", "quality check this", "panel review", "expert score", "evaluate this copy/strategy/page". For variant generation and multi-round conversion optimization see autoresearch; for live-URL CRO auditing see conversion-ops; for the scripted content-production pipeline see content-pipeline.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 21, 2026

See all skills by LazyIsEfficient

Report a problem with this skill