proposal

Plugin proposal from marketplace chwezi-proposal in peterbamuhigire/proposal-skills. Commands read from the repo's manifest — 2 days ago.

Skills (115)

• skills

  Use when routing, drafting, reviewing, or assembling a complete consulting proposal, EoI, bid, or tender response; use a numbered pipeline skill when only one known section is required.

• ai-agent-commercial-packaging

  Use when choosing whether an AI agent is included, sold as an add-on, or sold standalone; use the pricing skill for rate mechanics and the SLA skill for service commitments.

• ai-agent-contract-language-pack

  Use when selecting and adapting agent-specific contract exhibits for a proposal, MSA, or statement of work; use the addendum skill when drafting the full MSA/SLA overlay.

• ai-agent-intervention-credit-and-abort-refund

  Use when defining intervention credits, abort rights, or refund mechanics for an agent engagement; use the SLA skill for broader credits and the outcome-pricing skill for success fees.

• ai-agent-msa-and-sla-addendum-templates

  Use when drafting agent-specific MSA and SLA addendums covering action accountability, audit logs, kill switches, intervention, liability, and upstream-provider dependencies.

• ai-agent-procurement-objections-on-commercials

  Use when procurement, legal, or finance challenges agent pricing, failed-task billing, audit rights, refunds, liability, indemnities, or price corridors; use the contract pack for final clauses.

• ai-agent-renewal-and-true-up

  Use when defining renewal, volume true-up, ramp-down protection, autonomy-linked price steps, or indexation for an agent engagement; use the pricing skill for initial rates.

• ai-agent-sla-and-credit-schedule

  Use when defining an agent SLA and service-credit schedule for availability, task success, intervention rate, resolution time, kill-switch response, or audit-log access.

• ai-agent-success-fee-and-outcome-pricing

  Use when structuring agent gain-share, success-fee, base-plus-success, or performance-corridor pricing; use the general pricing skill for per-step, per-agent, or usage rates.

• ai-agent-business-case-and-roi

  Use when building a task-based business case for an AI agent, including intervention-adjusted benefits, the full agent cost stack, downside scenarios, and autonomy-ramp payback.

• ai-agent-change-management-and-adoption

  Use when planning workforce adoption, trust staging, supervisor training, affected-party disclosure, or contestability for agents that act on a buyer's behalf.

• ai-agent-compliance-credentials

  Use when presenting verified agent-specific trust and compliance credentials, including action logs, irreversibility gates, kill-switch drills, identity controls, and scope attestations.

• ai-agent-discovery-and-qualification

  Use when qualifying an AI-agent opportunity by testing agent-versus-workflow fit, autonomy level, action reversibility, oversight, accountability, success measures, and regulatory exposure.

• ai-agent-methodology

  Use when drafting the end-to-end delivery methodology for an AI agent or multi-agent system, from discovery and action-catalogue design through staged autonomy and operations.

• ai-agent-poc-and-pilot-scoping

  Use when scoping an AI-agent proof of concept or pilot with shadow, supervised, and agentic stages, measurable gates, abort conditions, and production-exit criteria.

• ai-agent-pricing-and-packaging-proposal

  Use when selecting and presenting per-resolution, per-outcome, per-step, per-agent, hybrid, or success-based pricing for an AI agent; use commercial-layer skills for contract exhibits.

• ai-agent-procurement-and-questionnaire

  Use when answering or pre-empting an AI-agent procurement questionnaire on autonomy, action scope, reversibility, kill switches, audit logs, identity, subprocessors, and governance.

• ai-agent-risk-and-responsible-ai

  Use when drafting an AI-agent risk register or responsible-AI commitment covering autonomous actions, irreversibility, scope, tool injection, identity, kill switches, and contestability.

• ai-agent-team-composition

  Use when defining an AI-agent delivery team, role accountabilities, RACI, mobilisation curve, safety coverage, client counterparts, or evaluator-facing staffing evidence.

• ai-agent-vertical-positioning

  Use when adapting an AI-agent proposal to customer support, finance, insurance, public sector, healthcare administration, legal support, or operations with a sector-specific autonomy stance.

• ai-on-saas-business-case-and-roi

  Use when an AI-on-SaaS proposal needs a CFO-grade ROI model that includes model usage, evaluation cost, risk-adjusted benefits, and downside scenarios; use the base SaaS ROI skill when no AI cost or quality variables apply.

• ai-on-saas-change-management-and-adoption

  Use when adoption planning must address trust, human oversight, escalation, retraining communications, and workforce concerns for AI features inside multi-tenant SaaS; use the SaaS rollout skill for non-AI operating change.

• ai-on-saas-combined-methodology

  Use when one proposal must integrate multi-tenant SaaS delivery with RAG, copilots, agents, or AI analytics across shared phases and gates; use SaaS implementation methodology when the scope contains no AI feature.

• ai-on-saas-compliance-credentials

  Use when a proposal must evidence AI-specific trust and compliance controls inside multi-tenant SaaS, including model providers, evaluation practice, data use, and region routing; use the SaaS trust skill for non-AI credentials.

• ai-on-saas-discovery-and-qualification

  Use when qualifying AI features inside a multi-tenant SaaS opportunity across workflow fit, data readiness, hallucination tolerance, regulation, and tenant variation; use SaaS discovery when no AI capability is proposed.

• ai-on-saas-poc-and-pilot-scoping

  Use when an AI feature inside SaaS needs a time-boxed POC or pilot with a golden dataset, measurable evaluation thresholds, abstention rules, and a production decision gate; use the SaaS pilot skill for non-AI trials.

• ai-on-saas-pricing-and-packaging-proposal

  Use when pricing AI features within SaaS through credits, allowances, overages, model tiers, or fair-use controls while protecting margin from usage and provider-cost volatility; use SaaS pricing when AI economics do not apply.

• ai-on-saas-procurement-and-questionnaire

  Use when an AI-on-SaaS bid must answer or pre-empt procurement questions about model providers, data training, retention, deletion, sub-processors, region routing, and sovereign options; use the SaaS questionnaire skill for non-AI review.

• ai-on-saas-risk-and-responsible-ai

  Use when an AI-on-SaaS proposal needs an owned AI risk register and auditable Responsible-AI commitment for CISO, DPO, ethics, or regulator review; use generic risk management when the engagement contains no AI.

• ai-on-saas-team-composition

  Use when an AI-on-SaaS proposal must justify the combined AI, data, safety, evaluation, platform, security, SRE, and customer-success roles required for delivery; use the standard team skill when no AI specialist roles are needed.

• ai-on-saas-vertical-positioning

  Use when AI-on-SaaS positioning must reflect a named vertical's use cases, regulator stance, evidence expectations, and risk language; use SaaS vertical positioning when AI-specific buyer concerns are absent.

• accounting-finance-advisory

  Use when a proposal covers accounting, finance operations, controls, ERP or POS finance, grants, tax, audit readiness, modelling, or financial transformation. Route pure bid pricing to 10-financial-proposal; this skill governs finance doctrine and delivery credibility.

• business-analysis-tools

  Use when a proposal needs diagnostic, requirements, options-appraisal, process, or decision-support tools. Unlike consulting-frameworks, this skill selects and applies business-analysis techniques to a defined analytical question and deliverable.

• capacity-building

  Use when a proposal requires training, coaching, mentoring, knowledge transfer, Training of Trainers, or institutional capacity development. Unlike change-management, this skill designs learning outcomes, delivery, assessment, and post-training transfer.

• change-management

  Use when a proposal must address adoption, resistance, readiness, communications, transition, or organisational reform. Unlike capacity-building, this skill governs behaviour and operating-model change rather than teaching competencies alone.

• consulting-frameworks

  Use when a proposal methodology needs a coherent conceptual framework, problem decomposition, or phase logic. Unlike business-analysis-tools, this skill shapes the overall consulting approach rather than selecting a technique for one analytical task.

• data-management

  Use when a proposal covers data collection, quality, governance, MIS, surveys, protection, retention, or migration. Route outcome measurement to monitoring-and-evaluation; this skill governs the data lifecycle and controls.

• eac-ecommerce-bds-programme-design

  Use when designing a donor-funded EAC e-commerce business-development-services programme, company-selection method, needs-assessment-to-technical-assistance pipeline, expert-pool deployment model, or results-based monitoring approach.

• environmental-and-social-safeguards

  Use when a proposal requires environmental or social screening, ESIA, ESMP, resettlement, donor safeguards, or national environmental compliance. Unlike gender-and-social-inclusion, this skill governs safeguard instruments, risk controls, and compliance evidence.

• gender-and-social-inclusion

  Use when a proposal needs gender analysis, GESI mainstreaming, disability inclusion, disaggregated indicators, or equitable participation. Unlike environmental-and-social-safeguards, this skill integrates inclusion into design and results rather than safeguard compliance instruments.

• giz-eu-local-procurement-response

  Use when responding to GIZ local procurement, EU/BMZ/GIZ tender packs, AVB/local application requirements, two-zip submissions, GIZ technical grids, self-declarations, price schedules, or GIZ clarification protocols.

• monitoring-and-evaluation

  Use when a proposal requires a theory of change, logframe, results framework, indicators, baselines, targets, learning, or evaluation. Unlike data-management, this skill defines performance questions and evidence use rather than the full data lifecycle.

• project-management

  Use when a proposal needs delivery governance, reporting, RACI, change control, escalation, or a project management plan. Unlike 08-work-plan, this skill governs how delivery is controlled, not merely when activities occur.

• retail-transformation-proposal

  Use when drafting a consulting proposal, EOI, bid, or methodology for retail, omnichannel, e-commerce, POS, merchandising, pricing, promotions, markdowns, loyalty, CRM, fulfilment, returns, store operations, shrink, vendor terms, private label, planogram, new-store opening, or retail KPI/WBR work.

• risk-management

  Use when a proposal requires risk identification, scoring, ownership, treatment, monitoring, or a risk register. Unlike project-management, this skill develops the assignment risk model and response thresholds rather than the full governance system.

• stakeholder-engagement

  Use when a proposal needs stakeholder mapping, consultation, participation, feedback, grievance handling, or engagement planning. Unlike change-management, this skill governs who must be heard and how their input is recorded, not adoption of a defined change.

• sustainability-planning

  Use when a proposal must explain institutional, technical, financial, or human-resource sustainability, handover, exit, or post-project support. Unlike capacity-building, this skill tests whether results continue after consultant withdrawal across all operating dimensions.

• east-african-english

  Use when drafting or reviewing English proposal content for Uganda, Kenya, Tanzania, or regional East African audiences; use language-standards when French or Kiswahili routing is also required.

• language-standards

  Use when a bilingual or multilingual proposal needs French or Kiswahili sections, translation checks, or one register and terminology policy across languages; use east-african-english for English-only tone work.

• ai-slop-audit

  Use when auditing an existing proposal artefact for AI slop after a major iteration or before submission; use anti-ai-slop instead as the live drafting guardrail.

• anti-ai-slop

  Use when producing any proposal or bid content to prevent generic, unverified, template-like writing in real time; use ai-slop-audit instead to grade an existing artefact after a major iteration.

• bid-red-team-dual-review

  Use when a high-stakes bid, tender response, EOI, or compliance-sensitive proposal section needs adversarial two-reviewer verification with a compliance rubric before it ships; use kaizen-improvement-system for the full engine/product audit and ai-slop-audit for the routine per-section gate.

• kaizen-improvement-system

  Use when auditing or improving the proposal engine or any bid, tender, EOI, methodology, technical/financial proposal, or consulting product it produces.

• operational-readiness-and-localisation

  Use when a proposal must prove locally executable operations across banking, tax, licensing, payroll, FX, compliance, logistics, privacy, government interface, or partnerships; use risk-management or financial-proposal for single-section drafting.

• skill-safety-audit

  Use when reviewing new or changed skills and bundled resources for unsafe installers, credential harvesting, hidden execution, or excessive permissions; use skill-writing for authoring structure.

• skill-writing

  Use when creating or normalising reusable proposal skills, trigger routes, contracts, references, or authoring automation under the canonical chwezi-dev-engine skill-writing standard; use skill-safety-audit instead for a read-only security review.

• submission-proof-and-receipt-discipline

  Use when a tender, EOI, or proposal submission has a deadline and a formal receipt requirement, to fix the exact submitted state, prove what was sent, when, to whom, and hold the confirmation; use the relevant submission checklist (e.g. giz-eu-local-procurement-response) for the mechanical pack chec

• update-claude-documentation

  Use when repository behaviour, routing, counts, validation, or release procedures change and README, AGENTS, CLAUDE, CONTRIBUTING, or focused docs must be synchronised; not for ordinary copy edits.

• 01-cover-letter

  Use when drafting a signed proposal transmittal or cover letter that confirms the assignment, authority, validity, and submission intent. Route bid synopsis to 02-executive-summary and shortlisting narratives to 09-expression-of-interest.

• 02-executive-summary

  Use when drafting the evaluator-facing summary of a full proposal: client problem, response, differentiators, scope, timing, and value. Unlike 01-cover-letter, this section synthesises the technical offer rather than transmitting it.

• 03-understanding-of-assignment

  Use when drafting the proposal's interpretation of context, objectives, scope, constraints, stakeholders, or ToR gaps. Unlike 06-methodology, this skill proves understanding of the problem before prescribing the delivery approach.

• 04-firm-profile

  Use when drafting the proposer or individual consultant profile, service areas, geographic presence, organisation, or credentials. Unlike 05-relevant-experience, this skill establishes enduring capability rather than assignment-by-assignment proof.

• 05-relevant-experience

  Use when drafting project sheets, assignment references, similarity evidence, outcomes, or an experience matrix. Unlike 04-firm-profile, this skill proves fit through verified past work selected against the evaluation criteria.

• 06-methodology

  Use when drafting the technical approach, conceptual model, phases, methods, QA, deliverables, or implementation logic, or when sizing sections to a page limit and scoring weights. Unlike 03-understanding-of-assignment, this skill explains how the work will be executed and verified.

• 07-team-composition

  Use when drafting staffing, roles, organograms, expert fit, CV framing, availability, or responsibility allocation. Unlike 08-work-plan, this skill proves that the proposed people can execute the methodology; it does not schedule their effort.

• 08-work-plan

  Use when drafting activities, dependencies, milestones, review gates, Gantt tables, or staffing schedules. Unlike 06-methodology, this skill converts the approach into an executable sequence and tests it against staffing and pricing.

• 09-expression-of-interest

  Use when drafting an EoI, REOI response, prequalification, or shortlisting submission focused on eligibility and relevant capability. Unlike a full proposal pipeline, this skill omits detailed methodology unless the notice explicitly requires it.

• 10-financial-proposal

  Use when drafting a bid budget, fee schedule, reimbursables, payment schedule, price form, or commercial assumptions. Unlike accounting-finance-advisory, this skill prices the proposed delivery and preserves any required technical-financial envelope separation.

• profiles

  Use when proposal drafting must select and enforce one proposer identity, voice, signatory, credential set, and branding rule; use the sector router separately for procurement and industry context.

• sectors

  Use when routing a proposal to the correct procurement-framework and industry-sector skills before drafting; use profiles separately to determine proposer identity and voice.

• afdb

  Use when an assignment is funded or governed by African Development Bank (AfDB) procurement, including ADB, ADF, or NTF windows, QCBS consultant selection and African-firm participation; use World Bank, UNDP, or PPDA skills when those rules control.

• agriculture

  Use when a proposal concerns agriculture, agribusiness, irrigation, value chains, extension, rural livelihoods, or food systems; use water-sanitation when WASH service delivery is the primary scope.

• civil-society-cyber-resilience

  Use when writing or reviewing a proposal for NGO or civil-society cybersecurity, digital resilience, incident readiness, or shared protection capacity; use risk-management for generic risk design and the ICT sector profile for technology-sector positioning.

• education

  Use when a proposal concerns education systems, TVET, teacher development, curriculum, edtech, institutional learning, or skills programmes; use governance when institutional reform is primary.

• energy

  Use when a proposal concerns power systems, electrification, renewable energy, utilities, clean cooking, energy access, or sector reform; use transport-infrastructure for roads, mobility, or civil infrastructure.

• financial-services

  Use when a proposal concerns banking, insurance, payments, mobile money, microfinance, digital finance, or financial inclusion; also apply the finance doctrine whenever money, ledger, tax, or accounting claims are in scope.

• governance

  Use when a proposal concerns institutional reform, decentralisation, accountability, anti-corruption, public financial management, or public-service delivery; use education or health when sector outcomes dominate.

• health

  Use when a proposal concerns public-health systems, health programmes, facilities, health informatics, pharmaceutical systems, or service improvement; use water-sanitation when WASH is the primary outcome.

• hospitality-hotel-restaurant

  Use when a proposal concerns a hotel, resort, lodge, inn, guest house, restaurant, bar, catering, event venue, or other hospitality operation.

• ict

  Use when a proposal concerns software, MIS, ERP, digital transformation, infrastructure, data platforms, cybersecurity, or e-government; use another sector skill as the lead when technology only supports its outcome.

• manufacturing-industrial
• ppda-uganda
• transport-infrastructure
• undp
• water-sanitation
• world-bank
• saas-business-case-and-roi-modeling
• saas-customer-success-and-adoption-proposal
• saas-discovery-and-qualification
• saas-implementation-methodology
• saas-lifecycle-communications-as-deliverable
• saas-multi-tenant-architecture-credibility-block
• saas-mutual-action-planning-and-close-plans
• saas-objection-handling-and-competitive-displacement
• saas-pilot-to-rollout-change-management
• saas-poc-and-pilot-scoping
• saas-pricing-and-packaging-proposal
• saas-procurement-and-security-questionnaire
• saas-trust-and-compliance-credentials-section
• saas-vertical-positioning
• ai-transformation-proposal
• critical-analysis-business-logic
• customer-service-and-maintenance-proposals
• embedded-accounting-engine-proposal
• key-account-pursuit-and-account-plan
• premium-client-proposal-strategy
• premium-pricing-and-value-defense
• proposal-storytelling-and-evaluator-journey
• sales-discovery-and-objection-handling
• service-design-proposal-strategy
• tender-orals-and-proposal-presentation
• website-design-proposal-strategy
• blog-idea-generator
• blog-writer
• premium-commercial-writing

Hooks (1)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/destructive-bash-gate.js"

Similar plugins