ferueda/implement-plan
skills/implement-plan/SKILL.md
Implement a spec document phase-by-phase, writing robust idiomatic code that follows codebase patterns.
$ install --global
skillsauthnpx skillsauth add ferueda/agent-skills implement-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 29, 2026, 3:00 AM23.8s1 file scanned
SKILL.md
- name:
- implement-plan
- description:
- Implement a spec document phase-by-phase, writing robust idiomatic code that follows codebase patterns.
Implement the given spec document. Work phase-by-phase, writing robust code that follows codebase patterns, and industry best practices and patterns.
Process
- Read the spec - Understand phases, success criteria, and scope boundaries
- Explore the codebase - Read files mentioned in the spec and related code
- Analyze patterns - Identify existing conventions, architecture, and idioms to follow
- Implement phase-by-phase - Complete each phase fully before proceeding
- Verify your work - Run
make checkafter code changes (skip for docs-only)
Implementation Rules
- Follow the plan - The spec is your contract; implement what's specified
- Match codebase patterns - Use existing conventions, not new ones
- Write robust code - Handle errors, edge cases, and failure modes
- Be idiomatic - Use language best practices and established patterns
- No shortcuts - Implement fully, don't stub or placeholder
Per-Phase Workflow
For each phase:
- Read - Understand what the phase requires
- Explore - Read existing code that will be modified or extended
- Implement - Write code matching codebase style and patterns
- Test - Run
make checkto verify (for code changes) - Update - Check off completed items in the spec file
Verification
- Code changes: Run
make checkbefore proceeding to next phase - On failure: Run
make fixfirst, then re-runmake check - Documentation-only: Skip verification
Communication
- If the plan doesn't match codebase reality, explain the discrepancy
- If you need to deviate, explain why before making changes
- Update checkboxes in the spec as you complete each section
Related Skills
ferueda/react-to-review
tools
VerifiedTrustedCommunity
Evaluate, analyze, and systematically react to an adversarial code review report. Decide on the action for each finding (Implement, Adapt, Decline), provide clear justifications, and define the plan to implement the accepted changes.
1SKILL.mdUpdated Jun 1, 2026
ferueda/theory-building
development
VerifiedTrustedCommunity
Manually invoked point-of-work workflow for applying Peter Naur's "programming as theory building" during active software work. Use this skill only when the user explicitly names `theory-building`, asks to use the theory-building skill, or explicitly says to apply programming-as-theory- building to the current design, implementation, refactor, review, or AI-generated code. Do not trigger automatically for ordinary architecture, implementation, refactor, review, debug, documentation, AI-code, domain model, or maintainability tasks.
1SKILL.mdUpdated May 29, 2026
ferueda/theory-building-review
development
VerifiedTrustedCommunity
Manually triggered weekly or post-change repository audit based on Peter Naur's "Programming as Theory Building." Use this skill only when the user explicitly names `theory-building-review`, asks to run the theory-building review skill, or says to run the weekly/post-change theory-building review. Do not trigger automatically just because the conversation mentions Naur, domain modeling, refactoring, architecture, craft, or code review. When explicitly invoked, inspect recent diffs or scoped repository areas, reconstruct the system theory, find places where code and domain language diverge, and return actionable refactor, test, documentation, and modeling improvements. For active design, implementation, refactor, review, or AI-code acceptance on a specific change, use `theory-building` instead when explicitly invoked.
1SKILL.mdUpdated May 29, 2026
ferueda/summarize-work
documentation
VerifiedTrustedCommunity
Summarize work done in a spec/plan document.
1SKILL.mdUpdated May 29, 2026