Review design documents for technical feasibility and architectural soundness.
npx skills add https://github.com/cloudfieldcz/cf-powers --skill review-as-dev
Please help me install this Agent Skill. Skill: review-as-dev Source: https://github.com/cloudfieldcz/cf-powers/tree/main/skills/review-as-dev Command: npx skills add https://github.com/cloudfieldcz/cf-powers --skill review-as-dev
This skill enables developers to review a technical analysis or specification from a developer perspective to validate feasibility, architecture, integration points, and security considerations.
Review the design document and codebase to verify feasibility, architecture, and integration before implementation.
High-intent search queries and answers about installing and using this skill.
Validate design feasibility by reviewing the technical specification against the actual codebase and explicit API contracts. This process confirms architectural soundness, verifies module boundaries, and ensures proper dependency handling before development begins.
A technical design review covers architecture, integration points, performance, and security. It identifies potential risks, verifies dependencies, checks API contracts to prevent breaking changes, and provides clear recommendations for the development project.
Verify API contracts and dependencies by checking the design document against the existing codebase during a technical review. This ensures proper handling of integration points, confirms DI patterns, and prevents breaking changes in module boundaries.
Yes, you can review security implications and performance risks within a technical specification. The analysis identifies potential security vulnerabilities and performance considerations while verifying the proposed architecture against the codebase.
You need a developer perspective technical analysis when you have a design document or specification ready for implementation. It confirms technical feasibility, validates integration points, and ensures the proposed architecture aligns with the actual codebase.
The best way to check module boundaries and integration points is through an architecture review of the design document. This verifies DI patterns, confirms explicit API contracts, and validates dependencies against the existing codebase.
tygwanDraft technical specifications with architecture, API contracts, and data models.
adolfoaranaes12Review architecture documents for risks and prioritized recommendations.
Serg28Automate security audits with semgrep, trivy, gitleaks, and dependency scanners.
vp-kEvaluate Flutter code review feedback against the codebase and implement changes incrementally.
