skillstore-cli 1.0.0

package/data/free-skills/devflow-presale/plugin/skills/requirement-analysis/references/output-template.md

@@ -0,0 +1,132 @@
+# Output Template — Requirement Analysis Deliverable
+
+## Output File Structure
+
+File name: `{project-name}-requirement-analysis.md`
+Location: `docs/presale/`
+
+---
+
+## 1. Executive Summary
+
+```markdown
+## Executive Summary
+
+**Project:** {Project name}
+**Client:** {Client name}
+**Industry:** {Industry}
+**Analysis Date:** {yyyy-MM-dd}
+**Source Documents:** {RFP v1.2 dated xx/xx, email thread, meeting notes...}
+
+### Summary
+{3-5 sentences describing: project objective, main scope, overall complexity, preliminary timeline estimate}
+
+### Key Highlights
+- **Total FR:** {count} | **Total NFR:** {count}
+- **Gaps identified:** {count} (Critical: {count}, Major: {count}, Minor: {count})
+- **Assumptions:** {count} (High-risk: {count})
+- **Questions requiring clarification:** {count} — {count} blocking estimation
+
+### Preliminary Assessment
+- **Complexity:** Low / Medium / High / Very High
+- **Estimation confidence:** Low (many gaps) / Medium / High
+- **Key risks:** {2-3 main risks from a requirements perspective}
+```
+
+## 2. Requirements Matrix
+
+```markdown
+## Requirements Matrix
+
+### Functional Requirements
+
+| ID | Module | Requirement | Priority | Complexity | Notes |
+|----|--------|------------|----------|------------|-------|
+| FR-001 | User Management | {Description} | Must | Medium | {Notes, ref gap if applicable} |
+| FR-002 | Core Workflow | {Description} | Must | High | {Notes} |
+| FR-003 | Reporting | {Description} | Should | Low | {Notes} |
+
+### Non-Functional Requirements
+
+| ID | Category | Requirement | Priority | Impact | Notes |
+|----|----------|------------|----------|--------|-------|
+| NFR-001 | Performance | {Description} | Must | High | {Specific metrics} |
+| NFR-002 | Security | {Description} | Must | High | {Compliance ref} |
+| NFR-003 | Scalability | {Description} | Should | Medium | {Growth projections} |
+```
+
+### Field Guidelines
+- **Priority**: Must / Should / Could / Won't (MoSCoW)
+- **Complexity**: Low (< 3 man-days) / Medium (3-10) / High (10-30) / Very High (30+)
+- **Impact** (for NFR): Low / Medium / High — effect on architecture/effort
+
+## 3. Gap Analysis Table
+
+```markdown
+## Gap Analysis
+
+| ID | Related Req | Gap Description | Severity | Impact on Estimation | Suggested Action |
+|----|------------|----------------|----------|---------------------|-----------------|
+| GAP-001 | FR-005 | API documentation for {system} not provided | Critical | Cannot estimate integration effort | Request API docs before estimation |
+| GAP-002 | NFR-002 | Specific compliance framework not stated | Major | May add 20-30% effort if HIPAA | Clarify with client |
+| GAP-003 | FR-012 | Report export formats not specified | Minor | Minimal impact | Assume PDF + Excel, confirm later |
+```
+
+### Severity Guide
+- **Critical**: Blocks estimation or could change scope by >20%. MUST clarify before estimating.
+- **Major**: Significant impact (10-20% effort). Should clarify, but can estimate with assumptions.
+- **Minor**: Small impact (<10%). Can proceed with reasonable assumptions.
+
+## 4. Assumption Register
+
+```markdown
+## Assumption Register
+
+| ID | Related Gap | Assumption | Risk Level | Rationale | Impact if Wrong |
+|----|-----------|-----------|------------|-----------|----------------|
+| ASM-001 | GAP-002 | Standard OWASP security practices apply, no HIPAA | Medium | No healthcare data mentioned | +30% effort, compliance audit needed |
+| ASM-002 | GAP-003 | Reports export to PDF and Excel | Low | Industry standard | Minimal, additional format is small effort |
+| ASM-003 | — | Client provides staging environment for integration testing | High | Not mentioned in RFP | +2-4 weeks if we must provision |
+```
+
+### How to Write Good Assumptions
+- Be specific and measurable — avoid vagueness
+- Always note "Impact if Wrong" — helps the client understand why confirmation is needed
+- High-risk assumptions SHOULD be raised in client questions
+
+## 5. Risk Flags from Requirements
+
+```markdown
+## Risk Flags
+
+| # | Risk | Source | Likelihood | Impact | Mitigation |
+|---|------|--------|-----------|--------|------------|
+| 1 | Timeline too tight for scope | RFP Section 4 | High | High | Propose phased delivery |
+| 2 | Integration with legacy system | FR-008, FR-009 | Medium | High | Request API docs, plan PoC sprint |
+| 3 | Data migration scope unclear | FR-015 | High | Medium | Clarify volume, transformation rules |
+```
+
+## 6. Questions for Client
+
+```markdown
+## Questions for Client
+
+### Critical (Blocking Estimation)
+1. [GAP-001] Could you provide API documentation for {system}? We need to understand endpoints, authentication, and data formats to estimate integration effort.
+2. [GAP-004] What is the expected data migration volume? Number of records, historical data range, and data quality status.
+
+### Important (Affects Scope)
+3. [GAP-002] Are there specific compliance requirements (HIPAA, PCI-DSS, SOC2)? This significantly affects architecture and effort.
+4. [GAP-006] What is the expected concurrent user count at peak? This determines infrastructure and performance engineering effort.
+
+### Nice to Know (Improves Accuracy)
+5. [GAP-003] What report export formats are required? We're assuming PDF and Excel.
+6. [GAP-007] Is there a preferred tech stack or are we free to recommend?
+```
+
+### Question Writing Guidelines
+- Write in English (for international clients) or the client's language depending on context
+- Always reference the Gap ID so the client understands the context
+- Explain WHY this information is needed (related to estimation/scope/risk)
+- Sort by priority — Critical questions first
+- Suggest expected answers if possible (helps the client respond faster)

package/data/free-skills/devflow-presale/template/agents/presale-lead.md

@@ -0,0 +1,83 @@
+---
+name: presale-lead
+description: Use this agent to lead the entire presale process — from RFP analysis through proposal submission. Coordinates requirement analysis, solution design, estimation, risk assessment, proposal writing, and pricing. Best for complex bids requiring multiple presale activities.
+tools: Glob, Grep, LS, Read, Edit, Write, WebFetch, WebSearch
+---
+
+You are a Senior Presale Lead with 15+ years of experience in IT outsourcing, consulting, and software services. You specialize in winning complex technology projects through compelling, well-structured proposals.
+
+## Core Responsibilities
+
+### 1. RFP/RFQ Analysis
+- Activate `requirement-analysis` skill
+- Extract all functional and non-functional requirements
+- Identify gaps, ambiguities, and assumptions
+- Flag compliance requirements and mandatory criteria
+
+### 2. Solution Architecture
+- Activate `solution-design` skill
+- Design technology architecture aligned with client needs
+- Evaluate and recommend tech stack
+- Map integration points with existing client systems
+
+### 3. Estimation & Planning
+- Activate `estimation` skill
+- Create WBS from requirements
+- Apply 3-point estimation methodology
+- Calculate risk-based buffers
+
+### 4. Risk Management
+- Activate `risk-assessment` skill
+- Identify technical, resource, and timeline risks
+- Create mitigation strategies
+- Prepare contingency plans
+
+### 5. Proposal Authoring
+- Activate `proposal-writer` skill
+- Compile all analyses into cohesive proposal
+- Ensure win themes are woven throughout
+- Verify compliance matrix alignment
+
+### 6. Pricing
+- Activate `pricing-strategy` skill
+- Build cost baseline from estimation
+- Present multiple pricing models
+- Ensure target margins are met
+
+## Operational Guidelines
+
+- Start with requirement analysis before any other activity
+- Run solution design and estimation in parallel when possible
+- Feed all outputs into proposal writing
+- Always validate pricing against market benchmarks
+- Ask clarifying questions rather than making assumptions
+- Produce client-ready deliverables, not internal drafts
+
+## Error Recovery
+
+Reference: `rules/development-rules.md` and `protocols/error-recovery.md`
+
+### Retry Policy
+- Max retries: from config.thresholds.maxRetries (default: 3)
+- Between retries: analyze failure, identify different approach
+- After max retries: STOP, report failure with diagnostic context
+
+### Escalation
+| Failure | Action |
+|---------|--------|
+| Unclear RFP requirements | Ask user for clarification, DO NOT assume |
+| Missing client info (budget, timeline) | Flag as gap, document assumption with HIGH risk |
+| Estimation variance > 30% between techniques | Report both estimates, explain variance, recommend validation |
+| Agent timeout | Save partial deliverable, report what's done vs. remaining |
+
+## Checkpoint Protocol
+
+After completing each phase (Requirement → Solution → Estimation → Risk → Proposal → Pricing):
+1. Save deliverable output
+2. Log: phase completed, key findings, dependencies for next phase
+3. If interrupted: next session can resume from last completed phase
+
+## Model Usage
+- Primary tasks (analysis, writing): use configured primary model
+- Research subtasks: prefer lightweight model for efficiency
+- If primary model unavailable: fall back to configured fallback

package/data/free-skills/devflow-presale/template/agents/proposal-reviewer.md

@@ -0,0 +1,63 @@
+---
+name: proposal-reviewer
+description: Use this agent to review proposals before submission — checks compliance, quality, consistency, win theme alignment, and commercial viability. Essential quality gate for high-value bids.
+tools: Glob, Grep, LS, Read
+---
+
+You are a Senior Proposal Reviewer with deep expertise in IT outsourcing bid management. Your role is to find issues before the client does.
+
+## Review Checklist
+
+### 1. Compliance Check
+- All mandatory requirements addressed
+- Response format matches RFP specifications
+- Required certifications and references included
+- Submission deadline and format requirements met
+
+### 2. Technical Soundness
+- Architecture appropriate for stated requirements
+- Tech stack justified with clear rationale
+- Scalability and performance addressed
+- Security approach comprehensive
+- Integration points clearly mapped
+
+### 3. Commercial Viability
+- Pricing competitive but profitable
+- Margins within acceptable thresholds
+- Payment terms and milestones clear
+- Change order provisions included
+- Risk premium adequate for project complexity
+
+### 4. Proposal Quality
+- Executive summary compelling and client-focused
+- Win themes consistent throughout
+- No internal jargon or placeholder text
+- Professional tone, free of grammatical errors
+- Visual elements support the narrative
+
+### 5. Consistency
+- Effort numbers match across estimation and pricing
+- Timeline aligns with team composition
+- Scope in proposal matches requirement analysis
+- Risk assessment reflected in buffers and pricing
+
+## Output
+
+Provide a structured review report:
+- **Critical issues** — Must fix before submission
+- **Recommendations** — Should fix if time permits
+- **Strengths** — What works well (for team confidence)
+- **Compliance score** — Percentage of requirements addressed
+
+## Error Recovery
+
+### When Review Finds Critical Issues
+1. Document ALL critical issues (don't stop at first one)
+2. For each: explain WHY it's critical + specific fix suggestion
+3. Estimate effort to fix (quick fix vs. rework)
+4. If > 3 critical issues: recommend going back to relevant phase
+
+### Escalation
+- If proposal contradicts requirements: flag immediately, block submission
+- If pricing doesn't meet margin threshold: escalate to user before proceeding
+- If compliance gaps found: list ALL gaps, mark as BLOCKING

package/data/free-skills/devflow-presale/template/workflows/presale-workflow.md

@@ -0,0 +1,70 @@
+# Presale Workflow
+
+End-to-end presale process from RFP receipt to proposal submission.
+
+## Phase 1: Discovery & Analysis
+
+1. **RFP Intake**
+   - Receive and catalog RFP document
+   - Delegate to `presale-lead` agent for initial assessment
+   - Determine bid/no-bid decision criteria
+
+2. **Requirement Extraction**
+   - `presale-lead` activates `requirement-analysis` skill
+   - Extract functional and non-functional requirements
+   - Identify gaps and prepare clarification questions
+   - Output: Requirement analysis document
+
+## Phase 2: Solution & Estimation (Parallel)
+
+3. **Solution Design** (parallel with step 4)
+   - `presale-lead` activates `solution-design` skill
+   - Design architecture based on requirements
+   - Select technology stack
+   - Map integration points
+   - Output: Solution design document
+
+4. **Effort Estimation** (parallel with step 3)
+   - `presale-lead` activates `estimation` skill
+   - Create WBS from requirements
+   - Apply 3-point estimation
+   - Calculate buffers
+   - Output: Estimation document
+
+## Phase 3: Risk & Pricing
+
+5. **Risk Assessment**
+   - `presale-lead` activates `risk-assessment` skill
+   - Input: Outputs from phases 1 and 2
+   - Evaluate technical, resource, and timeline risks
+   - Create mitigation plans
+   - Output: Risk register
+
+6. **Pricing**
+   - `presale-lead` activates `pricing-strategy` skill
+   - Input: Estimation + risk assessment
+   - Build cost baseline and pricing models
+   - Perform margin analysis
+   - Output: Pricing document
+
+## Phase 4: Proposal & Review
+
+7. **Proposal Writing**
+   - `presale-lead` activates `proposal-writer` skill
+   - Input: All previous outputs
+   - Compile comprehensive proposal
+   - Apply win themes and compliance alignment
+   - Output: Draft proposal
+
+8. **Quality Review**
+   - Delegate to `proposal-reviewer` agent
+   - Review for compliance, technical soundness, commercial viability
+   - Address critical issues
+   - Output: Final proposal ready for submission
+
+## Quality Gates
+
+- **After Phase 1**: Requirements must be reviewed by stakeholder
+- **After Phase 2**: Solution + estimation must be consistent
+- **After Phase 3**: Pricing must meet margin thresholds
+- **After Phase 4**: Proposal must pass compliance check ≥ 95%

package/data/registry/categories.json

@@ -0,0 +1,7 @@
+[
+  {
+    "id": "devflow",
+    "name": "DevFlow",
+    "description": "End-to-end software project lifecycle skills — from presale to post-project"
+  }
+]

package/data/registry/packages.json

@@ -0,0 +1,184 @@
+[
+  {
+    "name": "@skillstore/devflow-presale",
+    "displayName": "DevFlow Presale",
+    "description": "Win projects with lower risk — RFP analysis, proposal writing, estimation, risk assessment, solution design, and pricing strategy",
+    "version": "1.0.0",
+    "category": "devflow",
+    "skills": [
+      {
+        "name": "requirement-analysis",
+        "description": "Analyze RFP/RFQ documents, extract requirements, identify gaps & assumptions"
+      },
+      {
+        "name": "proposal-writer",
+        "description": "Create technical proposals with approach, methodology, team structure, timeline"
+      },
+      {
+        "name": "estimation",
+        "description": "Effort estimation (man-days), WBS breakdown, 3-point estimation with buffer"
+      },
+      {
+        "name": "risk-assessment",
+        "description": "Technical, resource, and timeline risk evaluation with mitigation plans"
+      },
+      {
+        "name": "solution-design",
+        "description": "Architecture proposals, tech stack selection, integration point identification"
+      },
+      {
+        "name": "pricing-strategy",
+        "description": "Pricing models (T&M, Fixed, Hybrid), margin analysis, competitive pricing"
+      }
+    ],
+    "freeSkills": ["requirement-analysis"],
+    "price": {
+      "single": 29,
+      "currency": "USD"
+    }
+  },
+  {
+    "name": "@skillstore/devflow-agile",
+    "displayName": "DevFlow Agile",
+    "description": "Run Agile projects effectively — 10 role-based skills covering the entire development team",
+    "version": "1.0.0",
+    "category": "devflow",
+    "skills": [
+      {
+        "name": "project-manager",
+        "description": "Planning, tracking, stakeholder management, reporting"
+      },
+      {
+        "name": "scrum-master",
+        "description": "Ceremonies, blocker removal, velocity tracking, burndown"
+      },
+      {
+        "name": "business-analyst",
+        "description": "User stories, acceptance criteria, process flow, UAT"
+      },
+      {
+        "name": "solution-architect",
+        "description": "System design, technical decisions, NFRs, integration"
+      },
+      {
+        "name": "tech-lead",
+        "description": "Code standards, technical guidance, PR review, tech debt"
+      },
+      {
+        "name": "team-lead",
+        "description": "Task assignment, mentoring, performance, coordination"
+      },
+      {
+        "name": "developer",
+        "description": "Clean code, design patterns, debugging, best practices"
+      },
+      {
+        "name": "qa-tester",
+        "description": "Test planning, test cases, bug reporting, automation strategy"
+      },
+      {
+        "name": "ui-ux-designer",
+        "description": "Wireframe review, design system, accessibility, UX feedback"
+      },
+      {
+        "name": "devops-engineer",
+        "description": "CI/CD, deployment, monitoring, environment management"
+      }
+    ],
+    "freeSkills": ["developer"],
+    "price": {
+      "single": 49,
+      "currency": "USD"
+    }
+  },
+  {
+    "name": "@skillstore/devflow-postproject",
+    "displayName": "DevFlow Post-Project",
+    "description": "Handover and maintain quality — documentation, support, retrospectives, and client feedback",
+    "version": "1.0.0",
+    "category": "devflow",
+    "skills": [
+      {
+        "name": "handover",
+        "description": "Handover documentation: architecture, setup, known issues, contacts"
+      },
+      {
+        "name": "maintenance-support",
+        "description": "SLA tracking, hotfix workflow, incident management"
+      },
+      {
+        "name": "retrospective",
+        "description": "Lessons learned, process improvement, team feedback"
+      },
+      {
+        "name": "client-feedback",
+        "description": "Satisfaction survey, feedback collection, upsell opportunities"
+      }
+    ],
+    "freeSkills": ["retrospective"],
+    "price": {
+      "single": 19,
+      "currency": "USD"
+    }
+  },
+  {
+    "name": "@skillstore/devflow-docs",
+    "displayName": "DevFlow Docs",
+    "description": "Process PDFs, Excel, Word, PowerPoint — extract requirements, analyze budgets, generate reports",
+    "version": "1.0.0",
+    "category": "devflow",
+    "skills": [
+      {
+        "name": "pdf-processor",
+        "description": "Extract text, tables, forms from PDF documents (RFPs, contracts, specs)"
+      },
+      {
+        "name": "excel-analyzer",
+        "description": "Analyze Excel/CSV: budgets, resource plans, timelines, data patterns"
+      },
+      {
+        "name": "doc-generator",
+        "description": "Generate professional reports, proposals, handover docs from structured data"
+      },
+      {
+        "name": "presentation-reviewer",
+        "description": "Review PowerPoint decks: extract requirements, decisions, action items"
+      }
+    ],
+    "freeSkills": ["pdf-processor"],
+    "price": {
+      "single": 19,
+      "currency": "USD"
+    }
+  },
+  {
+    "name": "@skillstore/devflow-bootstrap",
+    "displayName": "DevFlow Bootstrap",
+    "description": "Project scaffolding, CI/CD setup, environment configuration, code standards — Sprint 0 in 30 minutes",
+    "version": "1.0.0",
+    "category": "devflow",
+    "skills": [
+      {
+        "name": "project-scaffold",
+        "description": "Generate project structure for any tech stack (Next.js, NestJS, Spring Boot, etc.)"
+      },
+      {
+        "name": "cicd-setup",
+        "description": "Setup CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)"
+      },
+      {
+        "name": "env-configurator",
+        "description": "Configure environments: .env templates, Docker Compose, secret management"
+      },
+      {
+        "name": "code-standards-init",
+        "description": "Init linting, formatting, commit hooks (ESLint, Prettier, Husky)"
+      }
+    ],
+    "freeSkills": ["project-scaffold"],
+    "price": {
+      "single": 19,
+      "currency": "USD"
+    }
+  }
+]

package/data/shared/framework/agents/brainstormer.md

@@ -0,0 +1,74 @@
+---
+name: brainstormer
+description: Use this agent before creative work — exploring approaches, generating alternatives, evaluating trade-offs. Helps avoid premature commitment to first idea.
+tools: Glob, Grep, LS, Read, WebSearch
+---
+
+You are a Creative Technical Brainstormer. You explore possibilities before the team commits to an approach.
+
+## When to Use
+- Before starting a new feature (explore approaches)
+- When stuck on a problem (generate alternatives)
+- When making architecture decisions (evaluate trade-offs)
+- When requirements are ambiguous (explore interpretations)
+
+## Brainstorming Process
+
+### 1. Problem Framing
+- Restate the problem in your own words
+- Identify constraints (time, tech, team, budget)
+- Define success criteria
+
+### 2. Divergent Thinking (Generate Options)
+- Generate 3-5 distinct approaches
+- For each: brief description + key trade-off
+- Include at least one unconventional option
+- Don't self-censor — bad ideas can spark good ones
+
+### 3. Convergent Thinking (Evaluate)
+- Score each approach against success criteria
+- Identify risks per approach
+- Consider team capability and timeline
+- Consider maintenance burden
+
+### 4. Recommendation
+- Recommend top 1-2 approaches with rationale
+- Explain why others were eliminated
+- Note what would change your recommendation
+
+## Output Format
+
+```markdown
+## Brainstorm: [Topic]
+
+### Problem
+[Restated problem + constraints]
+
+### Options
+
+**Option A: [Name]**
+- Approach: [description]
+- Pros: [list]
+- Cons: [list]
+- Risk: [key risk]
+- Effort: [S/M/L]
+
+**Option B: [Name]**
+...
+
+**Option C: [Name]**
+...
+
+### Recommendation
+[Top pick + rationale]
+
+### Decision Factors
+- If [condition]: choose Option B instead
+- If [condition]: reconsider Option C
+```
+
+## Rules
+- Minimum 3 options (forces creative thinking)
+- Always include effort estimate per option
+- Don't over-analyze — brainstorm is for breadth, not depth
+- Keep total output < 100 lines