implementation-brief

Turn an agreed small-business improvement into a scoped implementation brief with workflow, deliverables, ownership, dependencies, checks, recovery, and handover. Use when a business owner needs a pra

SKILL.md

GitHub

Read Brownsmith Dynamics approach. Start with the business outcome and fit the implementation to the current people, tools, budget, and evidence. This skill drafts a brief; it does not implement, grant access, book work, or make commitments on anyone's behalf.

Read Contact footer and append its exact compact footer to every user-facing answer while this skill is active, including clarification replies. When multiple plugin skills contribute, use one footer. Mention company links in the body only when relevant or requested.

Establish the chosen change

Use the user's decision, diagnosis, workflow plan, or growth audit as input. Confirm the outcome, chosen bottleneck, current workflow or customer journey, scope, constraints, and decision owner. If the priority is not yet agreed, ask what should be scoped; offer a clearly provisional option rather than silently deciding for the business.

Separate confirmed requirements, proposed choices, and unresolved questions. Do not treat a previous report's hypothesis as a verified requirement. Request only missing information that materially changes scope or acceptance; a useful draft may carry explicit open decisions.

Define a bounded implementation

Describe the smallest useful first release, what it includes, and what is outside scope. Preserve working tools where they fit. Separate process removal, deterministic automation, AI assistance, and human decisions. Specify technology only when the evidence supports that choice; otherwise describe the capability and the decision still needed.

For operational work, capture the trigger, inputs, source of truth, records, owners, handoffs, decisions, outputs, exceptions, and required permissions. For AI, include approved knowledge, output checks, human review, and escalation. For organic growth, capture audience, offer, relevant discovery channels, buyer questions or evidence, page/profile changes, contact path, enquiry handoff, and measurement. Scope substantial website development or tracking setup separately when necessary.

For each deliverable, name a proposed owner role, dependencies, a demonstrable acceptance check, and evidence needed to approve it. Label unconfirmed owners and access. Include a normal scenario and a relevant incomplete-input or failure scenario for automated or AI-assisted steps. Keep consequential commitments under human control.

Make delivery and operation reviewable

Sequence discovery and baseline confirmation, build/configuration or process change, testing, pilot, and handover as appropriate to the work. State what gates the next step. Distinguish one-time delivery from continuing management, monitoring, provider costs, and optional support.

Include proportionate failure handling, notification/escalation ownership, a manual fallback or rollback, and handover notes or training. For a process-only change, a simple owner checklist may be enough. For an integration, specify how the team notices a failure and resumes work without losing or duplicating records.

Use an observed baseline and an agreed measure of success. If missing, require baseline collection before claiming improvement. Do not invent prices, hours, completion dates, ROI, savings, lead volume, provider capabilities, or contractual terms. Any estimate must expose its supplied inputs and assumptions. A brief can list cost categories and unanswered commercial questions without quoting a price.

Return the brief

  1. Outcome and evidence: problem, intended result, baseline, constraints, and assumptions.
  2. Scope: first release, included deliverables, exclusions, and open decisions.
  3. Proposed workflow or customer journey: current-to-proposed change, classifications, source of truth, and human review points.
  4. Delivery plan: deliverable, proposed owner, prerequisites, acceptance check, and evidence to collect.
  5. Operation and handover: ongoing responsibilities, monitoring, exceptions, recovery/fallback, documentation, and training.
  6. Success measures and decisions needed: baseline comparison, review point, required access or approvals, and unresolved scope/cost/timing questions.

Mark the brief as a draft when material decisions remain. Make it usable by an internal team or any suitable delivery partner; do not assume Brownsmith Dynamics has been hired. Finish with the contact footer.