technical-review
Skill4 starsChanged 3 months agoMITView on GitHub
Validate technical feasibility and claim realism (architecture, integration, ATO/cyber). Run --phase=approach after solution-architect; --phase=drafts after proposal-editor, before red-team.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- rmichak/claude-skillstheir own version, first seen Nov 8, 2026
- victor-falcon/skillstheir own version, first seen Nov 8, 2026
- TJM-NZ/claude-skillstheir own version, first seen Oct 11, 2026
- frameforged/technical-documentation-frameworktheir own version, first seen Jul 2, 2026
- RainLib/full-stack-skilltheir own version, first seen Mar 20, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- victor-falcon/skills★ 16same name
- frameforged/technical-documentation-framework★ 2same name
- rmichak/claude-skills★ 1same name
- RainLib/full-stack-skill★ 0same name
- TJM-NZ/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adversarial-reviewSkill
- capture-demand-signalsSkill
- capture-intentSkill
- capture-portal-structureSkill
- capture-scorecardSkill
- capture-submissionSkill
- competitor-assessmentSkill
- compliance-checkSkill
- customer-intelSkill
- dashboardSkill
- evidence-checkSkill
- export-proposalSkill
- import-from-captureSkill
- narrative-spineSkill
- new-proposalSkill
- opportunity-quick-lookSkill
- past-performanceSkill
- pricing-analystSkill
- proposal-editorSkill
- proposal-graphicsSkill
- proposal-managerSkill
- proposal-patcherSkill
- proposal-solution-architectSkill
- proposal-storyboardSkill
- proposal-writerSkill
- red-team-reviewSkill
- setup-companySkill
- statusSkill
- submission-summarySkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 84
Read in this order:
- Very specific: line 99
Do NOT read drafts/ at this phase.
- Distinctive: line 105
All approach-phase inputs (1-12 above)
- Very specific: line 107
All files in drafts/ — the bound, editor-polished section drafts (the editor edits these in place.
- Distinctive: line 271
Do not assume claims are true simply because they sound plausible.
- Distinctive: line 272
Prefer operational realism over marketing optimism.
- Distinctive: line 278
Do not rewrite for tone; rewrite for technical truthfulness.
- Distinctive: line 305
If not, flag it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Review Skill
Two-Phase Operation (mandatory dispatch)
This skill runs at two distinct points in the workflow. The phase determines inputs, scope, and output filename. If no phase is given, ask the user before proceeding.
| Mode | Position in workflow | Scope | Output |
--phase=approach | After /proposal-storyboard, BEFORE /proposal-writer | Validate architectural feasibility, integration realism, schedule/staffing realism, ATO plausibility, hidden assumptions — before tokens are spent on prose for a flawed approach | reviews/technical-review-approach.md |
--phase=drafts | After /proposal-writer and /proposal-editor, before /red-team-review | Validate claim truthfulness, technical-depth calibration, prose-level architecture consistency, hidden contradictions introduced during drafting | reviews/technical-review-drafts.md |
Critical rule: --phase=approach does NOT read drafts/. Drafts don't exist yet at that workflow position. Reading them invalidates the gate's purpose (the gate exists to prevent flawed approaches from becoming flawed prose).
--phase=drafts re-reads architecture and storyboard inputs because draft prose can introduce inconsistencies with the approved architecture (over-specified components, undefined interfaces, magical integrations) that need cross-checking.
Purpose
Perform an engineering and solution-integrity review of the proposal.
This skill is intentionally separate from:
- compliance review
- editorial review
- proposal scoring
- Shipley color-team review
The technical-review skill behaves like a skeptical chief engineer, solution architect, integrator, or program CTO reviewing the proposal for:
- technical accuracy
- architectural consistency
- feasibility
- integration realism
- deployment realism
- operational credibility
- ATO/security plausibility
- truthfulness of technical claims
- hidden execution risk
The goal is not to make the proposal prettier.
The goal is to ensure the proposal would survive contact with:
- customer engineers
- technical evaluators
- operational users
- program offices
- integration teams
- cybersecurity reviewers
- test events
- real deployment conditions
When to Use
Run twice:
- Approach phase — after
/proposal-storyboard, before/proposal-writer. Catches feasibility issues at the cheapest possible point. - Drafts phase — after
/proposal-editor, before/red-team-review. Catches claim-truthfulness issues introduced during prose generation.
Recommended workflow:
/proposal-solution-architect
/past-performance
/proposal-storyboard
/technical-review --phase=approach ← gate before writing
/proposal-graphics
/proposal-writer
/proposal-editor
/technical-review --phase=drafts ← gate before red team
/compliance-check
/red-team-review --mode=red
/red-team-review --mode=goldInputs
--phase=approach (pre-write feasibility gate)
Read in this order:
working/proposal-type.mdworking/proposal-plan.mdworking/requirement-matrix.mdworking/capability-matrix.mdworking/solution-strategy.mdworking/architecture-concept.mdworking/assumptions-and-risks.mdworking/storyboard.md(mandatory at this phase — if absent, exit and recommend running/proposal-storyboardfirst)working/capture-intent.mdif presentworking/competitor-assessment.mdif presentworking/compliance-matrix.mdif presentmy-company/evidence-ledger.jsonif present
Do NOT read drafts/ at this phase. They don't exist yet.
--phase=drafts (post-write claim-truthfulness review)
Read in this order:
- All approach-phase inputs (1-12 above)
working/graphics-brief.mdif present- All files in
drafts/— the bound, editor-polished section drafts (the editor edits these in place; there is no separatedrafts/edited/) reviews/editorial-changes.mdif presentreviews/technical-review-approach.md(the prior approach-phase report — flag any approach-phase findings that should have been addressed but weren't)
Review Philosophy
Assume the evaluator is technically competent and skeptical.
The technical-review skill should actively search for:
- hidden assumptions
- architecture inconsistencies
- hand-waving
- impossible timelines
- magical integrations
- unsupported scaling claims
- unrealistic staffing assumptions
- ambiguous deployment paths
- vague cybersecurity language
- claims that sound plausible but fail under scrutiny
This skill should behave like someone trying to break the proposal before the Government does.
Output Files
Phase-specific output filename:
| Phase | Output |
--phase=approach | reviews/technical-review-approach.md |
--phase=drafts | reviews/technical-review-drafts.md |
Optional supplementary output for either phase:
reviews/technical-risks.md
reviews/architecture-conflicts.mdThe drafts-phase review should explicitly cite the approach-phase report and flag any pre-write findings that became prose-level issues. Approach-phase issues that the writer ignored are higher severity than first-time-found drafts-phase issues.
Core Review Areas
Seven review areas. For each, ask the listed questions and flag any of the listed failure patterns. Severity is assigned per finding, not per area.
| # | Area | Goal | Key Questions | Flag Examples (issue -> why it matters) |
| 1 | Architecture Integrity | Architecture is internally consistent and technically plausible | Does the architecture support the operational claims? Are components/interfaces clearly defined? Does data flow make sense? Are dependencies acknowledged? Are DDIL/disconnected claims plausible? Are latency, edge-compute, and sync assumptions realistic? Are cloud/local responsibilities separated? Are external dependencies hidden? Is the runtime model deployment path believable? | "Local inference" but architecture depends on enterprise APIs -> contradiction; disconnected claim with hidden cloud dependency -> operational failure risk; unrealistic GPU/memory assumptions -> deployment infeasible; ambiguous data authority model -> integration/governance risk; undefined interface boundaries -> integration ambiguity |
| 2 | Integration Realism | Integration approach is operationally believable | Does the proposal assume unrealistic customer access? Are existing systems actually reachable? Are interfaces known or speculative? Is cross-domain movement realistic? Is integration effort underestimated? Are external vendor dependencies acknowledged? Is data normalization/governance ignored? Are assumed APIs guaranteed to exist? Is deployment inside customer infrastructure plausible? | "Integrates with existing systems" without naming mechanism -> hand-waving; assumes enterprise connectivity in tactical context -> mission mismatch; assumes direct access to classified systems -> unrealistic deployment; CDS integration described vaguely -> high execution risk |
| 3 | Operational Credibility | Proposal reflects real operational conditions | Are operational constraints acknowledged? Degraded connectivity? User/training burden? Perfect-data assumptions? Deployment realities? Sustainment burden? Workflow fit to operational tempo? Realistic operator experience? Is automation reliability overestimated? | Analysts manually curating large datasets -> unrealistic workflow; continuous synchronization -> operational mismatch; overstated autonomous behavior -> trust/control risk; ignored sustainment/training burden -> lifecycle credibility issue |
| 4 | Security / ATO / Cyber Realism | Cyber and accreditation language is technically believable | Are IL classifications used correctly? Are ATO claims specific and truthful? Is reciprocity described accurately? Cross-domain assumptions realistic? Is zero-trust language concrete? Data-handling boundaries clear? Identity/access assumptions believable? Model update/distribution security addressed? Software supply-chain risks ignored? | "ATO ready" without explanation -> buzzword compliance theater; reciprocity implied as automatic -> factually incorrect; loose IL5/IL6 use -> evaluator credibility hit; vague cross-domain language -> high-risk architecture gap |
| 5 | Timeline / Staffing / Execution Realism | Delivery plan is believable | Realistic schedule? Dependencies acknowledged? Believable staffing? Onboarding ignored? Government participation underestimated? Hardware lead times ignored? Test/integration cycles missing? RMF/ATO time ignored? Transition/sustainment underdeveloped? | Full deployment in 30 days with no integration assumptions -> unrealistic; no Government coordination -> delivery risk; aggressive staffing ramp -> resource credibility issue; ignored test event scheduling -> program realism gap |
| 6 | Technical Claim Truthfulness | Prevent technical exaggeration and accidental hallucination | Is every major claim supportable? Are superiority claims qualified? Are benchmarks contextualized? Are deployment claims specific? Are prototype claims presented as operational deployments? Is experimental functionality overstated? Is roadmap described as current capability? Are assumptions disguised as facts? | (See Claim Categories table below — every major claim must be classified.) |
| 7 | Technical Depth Calibration | Detail matches proposal type and audience | Too shallow? Too academic? Excessive implementation detail? Insufficient architecture detail? Customer-appropriate terminology? Explaining mechanisms the evaluator doesn't care about? Hiding important implementation realities? | Exec summary contains GPU/container detail -> move to technical approach; technical approach reads like marketing -> add architecture/process detail; white paper reads like FAR boilerplate -> compress and simplify; SBIR reads like product brochure -> add hypothesis and feasibility detail |
Area 6 — Claim Categories
Classify every major technical claim:
| Category | Meaning |
| Verified | Supported directly by evidence |
| Reasonable Inference | Likely true but partially inferred |
| Assumption | Depends on external conditions |
| Unsupported | No evidence found |
| High Risk | Likely to trigger evaluator skepticism |
| Prohibited | Should not appear in proposal |
Output the per-claim row in the Required Output Table:
| Claim | Classification | Risk | Recommended Action |
Technical Review Output Format
Write:
# Technical Review — [Proposal Name]
## Overall Technical Credibility Assessment
<2-4 paragraph assessment>
## Technical Risk Summary
| Severity | Count |
|---|---|
| High | X |
| Medium | X |
| Low | X |
---
## Findings
| ID | Severity | Category | Location | Issue | Why It Matters | Recommended Fix |
|---|---|---|---|---|---|---|
---
## Claim Truthfulness Review
| Claim | Classification | Evidence | Risk | Recommended Rewrite |
|---|---|---|---|---|
---
## Architecture Integrity Assessment
<assessment>
---
## Integration Realism Assessment
<assessment>
---
## Operational Credibility Assessment
<assessment>
---
## Security / ATO Assessment
<assessment>
---
## Timeline / Staffing Realism Assessment
<assessment>
---
## Highest-Risk Proposal Areas
1. <risk>
2. <risk>
3. <risk>
---
## Recommended Immediate Rewrites
<copy-paste-ready rewrites>Severity Standards
| Severity | Meaning |
| High | Likely evaluator concern or technical credibility hit |
| Medium | Real weakness or ambiguity that should be tightened |
| Low | Improvement opportunity or clarity issue |
Rules
- Be skeptical.
- Be technically grounded.
- Do not assume claims are true simply because they sound plausible.
- Prefer operational realism over marketing optimism.
- Flag hidden assumptions.
- Flag integration hand-waving.
- Flag architecture contradictions.
- Flag vague cybersecurity language.
- Flag magical AI claims.
- Do not rewrite for tone; rewrite for technical truthfulness.
Anti-Patterns to Catch
- "AI-enabled decision advantage" with no workflow explanation
- disconnected claims with hidden cloud dependency
- undefined data authority model
- unexplained synchronization behavior
- ATO implications stated casually
- CDS language without architecture detail
- "edge AI" with no hardware/runtime explanation
- unrealistic integration timelines
- vague references to autonomous agents
- undefined human-in-the-loop controls
- performance claims without constraints/context
- confusing prototype/demo with operational deployment
Final Test
Before finalizing, ask:
- Would a skeptical chief engineer believe this?
- Would a Government integrator see hidden work?
- Would the proposed deployment survive real operational conditions?
- Did the proposal accidentally promise magic?
- Would this survive a technical interchange meeting?
If not, flag it.
Activity Trail
Append to working/activity.md:
## <timestamp> — technical-review [<phase>] — identified <N findings>, <H high-risk>, reviewed architecture/integration/ATO realism → reviews/technical-review-<phase>.mdAppend to working/ai-runs.jsonl (note phase in notes):
{"schema_version":"ai-run.v1","timestamp":"<timestamp>","skill":"technical-review","proposal_id":"<proposal>","job_type":"technical-review","provider":"anthropic","model":"claude-opus-4-7","input_tokens_estimate":null,"output_tokens_estimate":null,"cost_estimate_usd":null,"notes":"phase=<approach|drafts> — architecture and execution realism review"}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

