agentsclimarketplace
Sign in

Project proposals

Skill shinzoxD/knackbox/skills/documents/project-proposals

Turn a rough initiative into a decision-ready project proposal with outcomes, scope, plan, costs, risks, and a clear approval request. Use whenever the user needs a business case, internal proposal, project charter, funding request, or stakeholder pitch, even if they only provide scattered notes or an idea.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill project-proposals

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.4 KB, 407 tokens by cl100k_base, as published. Nobody here has run it

Project Proposals

Write a proposal that helps a specific decision-maker decide whether to approve, fund, or prioritize the work.

Workflow

  1. Identify the decision, decision-maker, deadline, and approval threshold.
  2. Define the current problem with evidence and affected users.
  3. State measurable outcomes, not only deliverables.
  4. Bound in-scope and out-of-scope work.
  5. Describe the approach, milestones, owners, dependencies, and cost range.
  6. Compare viable alternatives, including doing nothing.
  7. Close with risks, mitigations, and a concrete decision request.

Output format

# <Proposal title>

## Decision requested
One sentence stating what should be approved, by whom, and by when.

## Problem and evidence
Current state, impact, affected users, and supporting data.

## Proposed outcome
Measurable success criteria and guardrails.

## Scope
### In scope
### Out of scope

## Approach and milestones
| Milestone | Owner | Target | Exit criteria |
|---|---|---|---|

## Cost and resources
People, systems, budget range, and assumptions.

## Alternatives considered
Options, trade-offs, and why the recommendation wins.

## Risks and mitigations
## Decision and next step

Rules

  1. Lead with the decision, not organizational history.
  2. Separate known facts, estimates, and assumptions.
  3. Use ranges when precise costs or dates are unsupported.
  4. Tie each deliverable to an outcome or remove it.
  5. Name the owner of every major dependency and risk response.
  6. Do not fabricate market data, customer quotes, savings, or ROI.

Edge cases

  • For an early idea, produce a one-page concept proposal and list the evidence required before a larger commitment.
  • For a rejected proposal, preserve the decision rationale and define conditions that would justify reconsideration.
  • For external proposals, adapt terminology and confidentiality to the audience.

What ships with it: 1 file

1.5 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.