Amfsa tech
Official@amfsa-tech
Offers technical documentation, codebase auditing, and structured development planning for engineering teams managing complex software lifecycles.
Agent Skills by Amfsa tech
Showing 10 vetted skills indexed across 1 GitHub repositories.
Amfsa-techwrite-a-prd
Generate a complete PRD from user interviews and codebase exploration.
Amfsa-techtriage-issue
Investigate codebases to create GitHub issues with TDD fix plans.
Amfsa-techfrontend-integration-guide
Generate frontend integration documentation from backend APIs and features.
Amfsa-techprd-to-plan
Convert PRDs into Markdown plan files with phased acceptance criteria.
Amfsa-techcode-audit
Identify bugs, unsafe logic, and architectural smells in codebases.
Amfsa-techrequest-refactor-plan
Create a refactoring plan with tiny commits and a GitHub issue.
Amfsa-techcodebase-analysis
Map a codebase's tech stack, structure, and data flow into a structured report.
Amfsa-techskill-creator
Guide users through planning, structuring, and packaging reusable Claude skills.
Amfsa-techtdd
Guide test-driven development through one-test-at-a-time cycles with minimal implementations.
Amfsa-techgrill-me
Walks through every branch of a decision tree to identify dependencies and hidden assumptions.
Frequently Asked Questions About Amfsa tech
FAQPage SchemaWhat specific engineering tasks are enabled by these capabilities?▼
These capabilities enable the generation of product requirement documents, the creation of structured refactoring plans, and the execution of test-driven development cycles. Users can perform deep codebase analysis to identify architectural smells, map data flows, and generate technical documentation for frontend integration based on existing backend structures.
Which personas benefit most from these technical skills?▼
Software engineers, technical leads, and product managers benefit from these skills. They are designed for developers needing to audit legacy codebases, architects planning complex refactoring efforts, and product owners requiring structured documentation and phased acceptance criteria derived directly from existing repository logic and codebase exploration.
What are the prerequisites for utilizing these planning and auditing skills?▼
Utilization requires access to a target codebase and a defined scope for the analysis or documentation task. Users must provide context regarding the repository structure or specific features to be audited, as the skills rely on direct codebase exploration to generate accurate PRDs, refactoring plans, or integration guides.