planning-code-goal-example-1-feature-implementation-plan
Sub-skill of planning-code-goal: Example 1: Feature Implementation Plan (+2).
Best use case
planning-code-goal-example-1-feature-implementation-plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of planning-code-goal: Example 1: Feature Implementation Plan (+2).
Teams using planning-code-goal-example-1-feature-implementation-plan should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/example-1-feature-implementation-plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How planning-code-goal-example-1-feature-implementation-plan Compares
| Feature / Agent | planning-code-goal-example-1-feature-implementation-plan | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of planning-code-goal: Example 1: Feature Implementation Plan (+2).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Example 1: Feature Implementation Plan (+2)
## Example 1: Feature Implementation Plan
```yaml
goal: implement_payment_processing_with_sparc
sparc_phases:
specification:
deliverables:
- requirements_doc
- acceptance_criteria
- test_scenarios
success_criteria:
- all_payment_types_defined
- security_requirements_clear
- compliance_standards_identified
pseudocode:
deliverables:
- payment_flow_logic
- error_handling_patterns
- state_machine_design
architecture:
deliverables:
- system_components
- api_contracts
- database_schema
refinement:
deliverables:
- unit_tests
- integration_tests
- implemented_features
success_criteria:
- test_coverage_80_percent
- all_tests_passing
completion:
deliverables:
- deployed_system
- documentation
- monitoring_setup
goap_milestones:
- setup_payment_provider:
sparc_phase: specification
preconditions: [api_keys_configured]
deliverables: [provider_client, test_environment]
success_criteria: [can_create_test_charge]
- implement_checkout_flow:
sparc_phase: refinement
preconditions: [payment_provider_ready, ui_framework_setup]
deliverables: [checkout_component, payment_form]
success_criteria: [form_validation_works, ui_responsive]
- add_webhook_handling:
sparc_phase: completion
preconditions: [server_endpoints_available]
deliverables: [webhook_endpoint, event_processor]
success_criteria: [handles_all_event_types, idempotent_processing]
```
## Example 2: Performance Optimization Goal
```yaml
goal: reduce_api_latency_50_percent
analysis:
- profile_current_performance:
tools: [profiler, APM, database_explain]
metrics: [p50_latency, p99_latency, throughput]
optimizations:
- database_query_optimization:
sparc_phase: refinement
actions: [add_indexes, optimize_joins, implement_pagination]
expected_improvement: 30%
success_metric: "p99 < 100ms"
- implement_caching_layer:
sparc_phase: architecture
actions: [redis_setup, cache_warming, invalidation_strategy]
expected_improvement: 25%
- code_optimization:
sparc_phase: refinement
actions: [algorithm_improvements, parallel_processing, batch_operations]
expected_improvement: 15%
```
## Example 3: Testing Strategy Goal
```yaml
goal: achieve_80_percent_coverage
current_coverage: 45
test_pyramid:
unit_tests:
target: 60%
sparc_phase: refinement
focus: [business_logic, utilities, validators]
integration_tests:
target: 25%
sparc_phase: completion
focus: [api_endpoints, database_operations, external_services]
e2e_tests:
target: 15%
sparc_phase: completion
focus: [critical_user_journeys, payment_flow, authentication]
milestones:
- milestone_55:
actions: [add_unit_tests_for_core_services]
deadline: "week 1"
- milestone_65:
actions: [add_integration_tests_for_api]
deadline: "week 2"
- milestone_80:
actions: [add_e2e_tests, increase_unit_coverage]
deadline: "week 3"
```Related Skills
plan-review-prompt-refresh-after-plan-edits
Refresh reviewer prompt files from the latest on-disk plan before every adversarial re-review. Prevents Codex/Gemini from critiquing stale plan text after local edits.
workspace-hub-overnight-plan-monitor
Monitor and reconcile workspace-hub overnight planning or implementation batches, including process status, result artifacts, issue/commit verification, and controlled failed-lane recovery.
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
read-only-pre-implementation-audit
Systematic cross-check workflow to validate assumptions before TDD coding begins
portable-baseline-pattern-implementation
Implement portable configuration baselines by separating machine-agnostic settings from machine-specific hooks and plugins
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
plan-gated-issue-implementation
Workflow for executing pre-approved GitHub issues with mandatory validation checkpoints
external-drive-ingest-planning
Plan safe external-drive ingests into repo-aligned storage such as /mnt/ace: read-only mounts, manifests, staged rsync, dedupe-merge gates, GitHub issue traceability, and governance/execution split.
user-approved-plan-state-sync
Reconcile GitHub and local repo state when a plan has been user-approved, including direct approval messages that require creating the local marker and moving the issue to status:plan-approved.
ten-agent-pre-plan-review-wave
Launch and verify a 10-agent planning-only wave that moves open GitHub issues into status:plan-review using one isolated worktree per issue, wave-specific continuation cron, and post-run artifact-reconciliation checks.