Remove docs/ and tasks/ directories

[ParkerRex]

Note

Removes the entire docs/ and tasks/ directories, deleting all documentation and planning files.

• Repo housekeeping:
  • Remove entire docs/ directory (API, auth, payments, deployment, guides, plans, reports, specs).
  • Remove tasks/ directory (issue task plan).
  • Eliminates all project documentation and planning files from the repo.

^{Written by Cursor Bugbot for commit fa7be66. This will update automatically on new commits. Configure here.}

[claude]

Claude finished @ParkerRex's task —— View job

---

PR Review: Remove docs/ and tasks/ directories

Review Tasks:

• Analyze the scope of documentation removal
• Assess impact on project maintainability
• Evaluate implications for new contributors
• Check if critical documentation was preserved elsewhere
• Provide comprehensive feedback and recommendations

---

🚨 Critical Issues Found

1. Missing Main Project README

Severity: HIGH

The project has no main README.md file. This is a critical gap for any project, especially one removing extensive documentation. The only README present is SKOOL_AUTOMATION_README.md, which covers only a specific feature.

Impact:

• New contributors have no entry point to understand the project
• No setup/installation instructions for the main application
• Missing project overview, architecture, and basic navigation
• GitHub repository appears incomplete without a main README

2. Massive Documentation Loss

Severity: HIGH

The PR removed 8,809 lines of comprehensive documentation across 36 files, including:

Critical Documentation Removed:

• CONTRIBUTING.md (326 lines) - Contribution guidelines
• API.md (495 lines) - API documentation
• AUTHENTICATION_SYSTEM.md (632 lines) - Auth architecture
• DEPLOYMENT.md (456 lines) - Deployment procedures
• IMPORT_BEST_PRACTICES.md (138 lines) - Code standards
• PAYMENTS.md (250 lines) - Payment system docs
• SKOOL_AGENT_IMPLEMENTATION.md (517 lines) - Core feature docs
• SKOOL_API_SPEC.md (656 lines) - API specifications

Technical Documentation Lost:

• Architecture decision records (ADRs)
• Data integrity reports
• Schema field usage reports
• Issue planning documents
• Feature implementation guides

3. No Knowledge Preservation Strategy

Severity: MEDIUM

The removal appears to be part of tooling migration (tooling/migrate-to-bun-biome branch) but lacks:

• Migration of critical content to new locations
• Preservation of institutional knowledge
• Alternative documentation strategy

---

What Remains

Preserved Documentation:

• SKOOL_AUTOMATION_README.md - Well-structured feature documentation (7,735 lines)
• features/news/README.md - Comprehensive feature docs (251 lines)
• scripts/MIGRATION_README.md - Migration procedures
• CODE_OF_CONDUCT.md - Community guidelines
• .claude/ directory - Claude Code agent configurations

Development Infrastructure:

• package.json with proper scripts (lint, typecheck, test, build)
• Biome configuration for linting/formatting
• TypeScript configuration
• Test framework setup

---

Recommendations

🔥 Immediate Actions Required

1. Create Main README.md

# Project Name
Brief project description

## Quick Start
- Installation steps
- Development setup
- Basic usage

## Architecture
- High-level overview
- Key technologies
- Project structure

## Contributing
- How to contribute
- Development workflow
- Code standards

## Documentation
- Link to feature docs
- API references
- Deployment guides

2. Preserve Critical Knowledge
Extract and preserve essential content from removed docs:

• Authentication system architecture
• API specifications
• Deployment procedures
• Contributing guidelines

3. Establish Documentation Strategy

• Define documentation standards
• Create centralized documentation hub
• Implement documentation review process

⚠️ Security & Best Practices

No Security Issues Found - The changes only remove documentation files, no code modifications that could introduce vulnerabilities.

Code Quality: N/A - No code changes to review.

Performance: N/A - Documentation removal has no performance impact.

Test Coverage: No changes to test files, but removed docs may have contained testing procedures.

---

Migration Assessment

Positive Aspects

• ✅ Clean removal of outdated/redundant documentation
• ✅ Part of systematic tooling migration to Bun/Biome
• ✅ Preserved feature-specific documentation
• ✅ Maintained development tooling

Concerns

• ❌ No main README created
• ❌ No knowledge migration strategy
• ❌ Loss of institutional knowledge
• ❌ Reduced contributor onboarding materials

---

Overall Assessment

Status: ⚠️ NEEDS IMMEDIATE ATTENTION

While the tooling migration and documentation cleanup may be justified, the complete removal without replacement creates significant gaps. The project needs urgent attention to:

1. Create a main README - Essential for project visibility and onboarding
2. Preserve critical knowledge - Extract key information from removed docs
3. Establish documentation standards - Prevent future documentation debt

Recommendation: Consider this PR as phase 1 of documentation reorganization, with immediate follow-up to address the gaps identified above.

---

[claude]

Code Review for PR #147: Remove docs/ and tasks/ directories

⚠️ Critical Issues Found

While this PR successfully removes the documentation directories, it creates several breaking references that need to be addressed:

1. Broken Documentation References 🔴

The following files still reference the deleted documentation:

In .claude/CLAUDE.md:274-276:

• References to docs/SKOOL_API_SPEC.md
• References to docs/SKOOL_POSTING_GUIDE.md
• References to docs/SKOOL_AUTOMATION_SETUP.md

In lib/skool-poster.ts:8,259:

• JSDoc comment references docs/SKOOL_POSTING_GUIDE.md
• Error message directs users to non-existent documentation

In lib/skool-agent.ts:7:

• JSDoc comment references docs/SKOOL_API_SPEC.md

In SKOOL_AUTOMATION_README.md:159-160,333-334:

• Multiple references to deleted documentation files

In .claude/commands/work-on-issue.md:7:

• References task planning in /docs/issues/ directory

2. Lost Critical Documentation 📚

The deleted documentation included essential information:

• API specifications (495 lines of API documentation)
• Authentication system guide (632 lines)
• Payment system documentation (250 lines)
• Deployment guide (456 lines)
• Skool automation setup (386+ lines)
• Contributing guidelines (326 lines)

3. Impact on Developer Experience 👨‍💻

• New developers will lack onboarding documentation
• No reference for API usage patterns
• Missing setup instructions for Skool automation features
• No architectural decision records (ADRs)

Recommendations

1. Update all references: Search and update all files that reference the deleted documentation paths
2. Consider migration strategy: If docs are being moved elsewhere (e.g., external wiki, README consolidation), update references accordingly
3. Preserve critical docs: Consider keeping essential setup/API documentation in the repo or provide alternative locations
4. Update CLAUDE.md: The AI assistant configuration still references these docs and will fail when trying to access them

Files Requiring Updates

• lib/skool-poster.ts
• lib/skool-agent.ts
• SKOOL_AUTOMATION_README.md
• .claude/CLAUDE.md
• .claude/commands/work-on-issue.md

Conclusion

While cleaning up documentation can be beneficial, this PR creates broken references that will impact both development workflows and the AI assistant's ability to provide accurate help. Please address the broken references before merging, or consider a phased approach where references are updated first.